Information input apparatus

ABSTRACT

An information input apparatus including a user interface that detects a first input operation and a processor that assigns information to each of a plurality of directions from a position centered at the first input operation detected by the user interface. The user interface detects a second input operation corresponding to one of the plurality of directions, and the processor selects information assigned to the one of the plurality of directions as an input.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of and is based upon and claims thebenefit of priority Under 35 U.S.C. §120 for U.S. Ser. No. 13/247,541,filed Sep. 28, 2011 and claims the benefit of priority of ProvisionalApplication Ser. No. 61/442,032, filed Feb. 11, 2011, the entirecontents of which are incorporated herein by reference.

BACKGROUND

1. Field of the Disclosure

The present disclosure relates to an information input apparatusprovided with what is called a touchscreen, and configured to enableinput of various information such as text characters, for example, byuser operations on the touchscreen.

2. Description of Related Art

In the case of a conventional keypad-type character input methodimplemented in mobile phone devices, the 26 characters of the alphabetand several other symbols are severally grouped under respectivenumerals, with one key being assigned to each of these groups, forexample.

With the keypad-type character input method, as a first step, the userfirst presses a key assigned to the group to which belongs thecharacter, etc. that he or she wants to input. Next, as a second step,if the user repeatedly presses that key, the characters, etc. in thegroup assigned to the key are switched in order and become selectableaccording to the number of key presses. Then, as a third step, the userstops pressing the key when the switched in, selectable character hasbecome the desired character. In so doing, input of a desired alphabeticcharacter or a desired symbol becomes possible.

In the case of this character input method, multiple key pressoperations become necessary in order to select a character the userwants to input, and the user must conduct the vexing work of repeatedkey press operations.

For this reason, a character input method enabling input of singlecharacters by single key operation actions is proposed in JapaneseUnexamined Patent Application Publication No. 2006-238171 (PatentCitation 1), for example.

In the case of the character input method disclosed in the above patentapplication publication, the 26 characters of the alphabet and severalother symbols, for example, are severally grouped under respectivenumerals, with one key being assigned to each of these groups, similarlyto the conventional keypad-type character input method.

Then, with a character input sequence for this character input method,as a first step, the user first presses a key assigned to a group towhich belongs the character, etc. that he or she wants to input. Next,as a second step, if the user keeps holding down that key, thecharacters, etc. in the group assigned to the key are switched in orderat a fixed time interval and become selectable according to the amountof time the key is continuously held down. The user stops pressing thekey and removes his or her finger, etc. from the key when the desiredcharacter is reached. In so doing, input of a desired alphabeticcharacter or a desired symbol becomes possible.

In so doing, input of a desired alphabetic character or a desired symbolbecomes possible.

Meanwhile, in the case where Japanese characters are input with thecharacter input method disclosed in the above patent applicationpublication, the respective characters in an individual “column” underan individual “row” of the gojuon syllabary are formed into a singlegroup, with one key being assigned to each “row”. Then, in a first step,the user presses a key assigned to a group of the “row” to which belongthe character, etc. that he or she wants to input. Next, as a secondstep, if the user keeps holding down that key, the characters in each“column” in the “row” group assigned to the key are switched in order ata fixed time interval and become selectable according to the amount oftime the key is continuously held down. The user stops pressing the keyand removes his or her finger, etc. from the key when the desiredcharacter is reached. In so doing, a Japanese character is input.

SUMMARY OF THE DISCLOSURE

However, in the case of the character input method disclosed in thepatent application publication described above, there is a problem inthat it forces input work that is dependent on timings set in thecharacter input apparatus, regardless of the user's intentions.

In other words, in the case where the character, etc. that the userwants to input is positioned lower in the order in a given group, theuser must keep pressing a key until the character in that group becomesselectable, and the user must wait a somewhat long amount of time untilthe desired character becomes selectable. Also, when the desired key hasbecome selectable, the user is required to do the work of releasing hisor her finger from the key in accordance with that timing. If the usermisses the timing, then he or she must wait even more until the desiredcharacter becomes selectable again. Furthermore, the timing at which thedesired character becomes selectable depends on its rank within thegroup. For this reason, the timing for holding down and then released akey differs for each character, and the user must pay careful attentionto match the timing for inputting a desired character.

Meanwhile, in recent years there have appeared information terminalsprovided with a touch panel on top of a display panel, for example,instead of what is called a keypad. Such information terminals enablecharacter input, etc. by operating the touch panel. It is alsoconceivable for the character input method disclosed in the above patentapplication publication to be implemented as a character input methodfor a mobile information device provided with such a touch panel. Inother words, in this case, a plurality of virtual keys, etc.respectively corresponding to each group are displayed on a displayprovided with a touch panel, and after confirming from among the virtualkeys the position of the virtual key for the group to which a desiredcharacter belongs, the user touches the area above that virtual key.Then, the user maintains the touch state with that virtual key until thedesired character becomes selectable, and when he or she has visuallyconfirmed that the desired character has become selectable, the usercancels the touch state (removes his or her finger). In this way, duringcharacter input, the user must wait a somewhat long amount of time untila desired character becomes selectable, and he or she must pay carefulattention to match the timing for inputting a desired charactersimilarly to that described above, even with an information deviceprovided with a touch panel. Particularly, the burden becomes extremelylarge in the case of this example, since the user must confirm by sightboth the position to be touched and the timing when to cancel the touchstate.

Given the above, the Inventor is aware of the need for an informationinput apparatus able to greatly reduce the burden on the user when usinga touch panel to input characters, etc. on an information inputapparatus provided with a touch panel on top of a display panel, forexample, whereby the work of visual confirmation by the user can bedecreased, and the burden of timing matching when inputting is made tobe mostly unnecessary.

Thus, an information input apparatus of an embodiment of the presentdisclosure includes a user interface configured to detect a first inputoperation; a processor configured to assign information to each of aplurality of directions from a position centered at the first inputoperation detected by the user interface, wherein the user interface isconfigured to detect a second input operation corresponding to one ofthe plurality of directions, and the processor is configured to selectinformation assigned to the one of the plurality of directions as aninput.

According to another exemplary embodiment, the disclosure is directed toa method of controlling a user interface of an information inputapparatus, the method comprising: detecting, at a user interface of theinformation input apparatus, a first input operation by a user;assigning, by a processor of the information input apparatus,information to each of a plurality of directions from a position of thefirst input operation detected by the user interface; detecting, by theuser interface, a second input operation by the user corresponding toone of the plurality of directions; and selecting, by the processor,information assigned to the one of the plurality of directions as aninput.

According to another exemplary embodiment, the disclosure is directed toa non-transitory computer-readable medium including computer programinstructions, which when executed by an information input apparatus,cause the information input apparatus to perform a method, the methodcomprising: detecting a first input operation by a user; assigninginformation to each of a plurality of directions from a position of thefirst input operation detected by the user interface; detecting a secondinput operation by the user corresponding to one of the plurality ofdirections; and selecting information assigned to the one of theplurality of directions as an input.

In an embodiment of the present disclosure, the user can perform inputoperations at a desired position on a detection surface of an inputoperation unit.

Consequently, according to an embodiment of the present disclosure, inthe case where, as an example, the user inputs characters, etc. using atouch panel in an information device provided with a touch panel, etc.on a display panel, the work of visual confirmation by the user becomesmostly unnecessary and also timing matching during input is unnecessary,thereby enabling information input with an extremely low burden.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram that illustrates an exemplary schematicinternal configuration of a mobile information device of an embodimentof the present disclosure.

FIG. 2 is a diagram that illustrates an example wherein a mobileinformation device of the present embodiment is in a browser screenmode, and a browser screen with a text box and a search button disposedthereon is displayed on a display screen.

FIG. 3 is a diagram that illustrates a state wherein the user has tappedthe area above a text box in browser screen mode.

FIG. 4 is a diagram that illustrates an exemplary takeover mode screenwhen a mobile information device of the present embodiment enters a fullscreen takeover mode.

FIG. 5 is a diagram that illustrates the position of a finger contactpoint when the user contacts his or her finger with a desired positionin the case where a mobile information device of the present embodimenthas entered a full screen takeover mode.

FIG. 6 is a diagram used to explain the position of a finger contactpoint when the user contacts his or her finger with a desired position,as well as a group object group and flick directions corresponding tothat position during an English character keypad-relative input mode.

FIG. 7 is a diagram used to explain how a desired character group isselected by a flick gesture during an English character keypad-relativeinput mode.

FIG. 8 is a diagram used to explain how a desired character group isselected by the user by means of a flick gesture during an Englishcharacter keypad-relative input mode.

FIG. 9 is a diagram that illustrates a takeover mode screen in a standbystate with respect to a second flick gesture during an English characterkeypad-relative input mode.

FIG. 10 is a diagram that illustrates the position of a finger contactpoint when the user contacts his or her finger with a desired positionon a takeover mode screen in a standby state with respect to a secondflick gesture during an English character keypad-relative input mode.

FIG. 11 is a diagram used to explain the position of a finger contactpoint when the user contacts his or her finger with a desired position,as well as a character object group and flick directions correspondingto that position for a second flick gesture during an English characterkeypad-relative input mode.

FIG. 12 is a diagram used to explain how a desired character group isselected by a second flick gesture during an English characterkeypad-relative input mode.

FIG. 13 is a diagram used to explain how a desired character is selectedby the user by means of a second flick gesture during an Englishcharacter keypad-relative input mode.

FIG. 14 is a diagram that illustrates a state wherein a character “x”and a cursor following the character are displayed in a current inputtext display area and a text box due to the character “x” beingselected, for example.

FIG. 15 is a diagram that illustrates a state wherein for example thecharacters up to “xm” from the characters in “xmas” have been input.

FIG. 16 is a diagram that illustrates a state wherein the input of allthe characters in “xmas” has finished.

FIG. 17 is a diagram that illustrates a screen of a browser screen modeafter the input of all the characters “xmas” has finished.

FIG. 18 is a diagram that illustrates the position of a finger contactpoint when the user contacts his or her finger with a desired positionduring a Japanese character input mode.

FIG. 19 is a diagram used to explain the position of a finger contactpoint when the user contacts his or her finger with a desired position,as well as a group object group and flick directions corresponding tothat position during a Japanese character input mode.

FIG. 20 is a diagram used to explain how a desired character group isselected by a flick gesture during a Japanese character input mode.

FIG. 21 is a diagram used to explain how a desired character group(consonant) is selected by the user by means of a flick gesture during aJapanese character input mode.

FIG. 22 is a diagram that illustrates a takeover mode screen in astandby state with respect to a second flick gesture during a Japanesecharacter input mode.

FIG. 23 is a diagram used to explain the position of a finger contactposition when the user contacts his or her finger with a desiredposition, as well as a character object group and flick directionscorresponding to that position for a second flick gesture during aJapanese character input mode.

FIG. 24 is a diagram used to explain how a desired character group isselected by a second flick gesture during a Japanese character inputmode.

FIG. 25 is a diagram used to explain how a desired character group isselected by a second flick gesture during a Japanese character inputmode.

FIG. 26 is a diagram that illustrates a state wherein for example anunconfirmed character “ke” and a cursor following the character aredisplayed in a current input text display area and a text box during aJapanese character input mode.

FIG. 27 is a diagram that illustrates a state wherein the unconfirmedcharacters “kensaku” and a cursor following the characters are displayedin a current input text display area and a text box during a Japanesecharacter input mode.

FIG. 28 illustrates how a convert/symbol instruction area is tappedduring a Japanese character input mode.

FIG. 29 is a diagram that illustrates an example wherein a conversionkanji candidate list corresponding to the unconfirmed characters“kensaku” is displayed on a display screen.

FIG. 30 is a diagram that explains how a flick gesture is conductedwhile in a state wherein a conversion kanji candidate list correspondingto the unconfirmed characters “kensaku” is displayed on a displayscreen.

FIG. 31 is a diagram that illustrates an example wherein a conversionkanji candidate list is displayed on a display screen after scrolling bya flick gesture.

FIG. 32 is a diagram that illustrates how the user's finger contacts atouch panel at a position corresponding to a user-desired conversionkanji candidate from a conversion kanji candidate list.

FIG. 33 is a diagram that illustrates how the user conducts a flickgesture at a position corresponding to a user-desired conversion kanjicandidate from a conversion kanji candidate list.

FIG. 34 is a diagram that illustrates a state wherein the characters“KENSAKU” are displayed in a current input text display area and a textbox due to a user-desired conversion kanji candidate being selected froma conversion kanji candidate list.

FIG. 35 is a diagram that illustrates a state wherein the characters“KENSAKU suru” are displayed in a current text display area and a textbox during a Japanese character input mode.

FIG. 36 is a diagram used to explain the position of a finger contactpoint when the user contacts his or her finger with a desired position,as well as a numeral object group and flick directions corresponding tothat position during a numeral input mode.

FIG. 37 is a diagram that illustrates an example wherein a mobileinformation device of the present embodiment has entered a musicplayback mode, and wherein the currently playing song title and playbacktime are displayed on a display screen.

FIG. 38 is a diagram that illustrates the position of a finger contactpoint when the user contacts his or her finger with a desired positionduring a music playback mode.

FIG. 39 is a diagram used to explain the position of a finger contactpoint when the user contacts his or her finger with a desired position,as well as a menu group object group and flick directions correspondingto that position during a music playback mode.

FIG. 40 is a diagram used to explain how a desired menu group isselected by the user by means of a flick gesture during a music playbackmode.

FIG. 41 is a diagram that illustrates a state wherein a bar object isdisplayed on a takeover mode screen after a volume control menu group isselected by the user during a music playback mode.

FIG. 42 is a diagram that illustrates the position of a finger contactpoint when the user contacts his or her finger with a desired positionafter a volume control menu group is selected during a music playbackmode.

FIG. 43 is a diagram used to explain the position of a finger contactpoint when the user contacts his or her finger with a desired position,as well as a menu object group and flick directions corresponding tothat position after a volume control menu group is selected during amusic playback mode.

FIG. 44 is a diagram used to explain how a “Low” volume menu item isselected from among volume control menu items during a music playbackmode.

FIG. 45 is a diagram that illustrates a state wherein a bar object isdisplayed on a takeover mode screen after a “Low” volume menu item isselected from among volume control menu items during a music playbackmode.

FIG. 46 illustrates an exemplary display screen during an informationsearch mode for the case wherein the search target is set to a phonebook.

FIG. 47 is a diagram that illustrates the position of a finger contactpoint when the user contacts his or her finger with a desired positionduring an information search mode.

FIG. 48 is a diagram used to explain the position of a finger contactpoint when the user contacts his or her finger with a desired position,as well as a group object group and flick directions corresponding tothat position during an information search mode.

FIG. 49 is a diagram used to explain how a desired group object isselected by the user by means of a flick gesture during an informationsearch mode.

FIG. 50 is a diagram that illustrates an example wherein a searchinformation list of registered names, etc. extracted from a phone bookis displayed due to the consonant “k” being selected by the user duringan information search mode.

FIG. 51 is a diagram that illustrates the position of a finger contactpoint when the user contacts his or her finger with a desired positionon a display screen of a search information list of registered names,etc. extracted from a phone book on the basis of the consonant “k”during an information search mode.

FIG. 52 is a diagram used to explain the position of a finger contactpoint when the user contacts his or her finger with a desired position,as well as a group object group and flick directions corresponding tothat position on a display screen of a search information list based onthe consonant “k” during an information search mode.

FIG. 53 is a diagram used to explain how a desired group object isselected by the user by means of a flick gesture on a display screen ofa search information list based on the consonant “k” during aninformation search mode.

FIG. 54 is a diagram that illustrates an example wherein a searchinformation list is displayed after the search is further refined due tothe consonant “s” being additionally selected by a flick gesture on adisplay screen of a search information list based on the consonant “k”during an information search mode.

FIG. 55 is a diagram that illustrates an exemplary display when thesearch information becomes a single entry due to the search beingfurther refined due to the consonant “n” being additionally selected bya flick gesture on a display screen of a search information list basedon the consonant “k” and the consonant “s” during an information searchmode.

FIG. 56 is a diagram for explaining an example of consecutive flickgestures performed in a state wherein a finger is not released from atouch panel.

FIG. 57 is a diagram that illustrates an input event—input IDcorrespondence table for a mobile information device of the presentembodiment to recognize tap gestures with respect to a touch panel andrespective flick directions for flick gestures during respectivecharacter input modes.

FIG. 58 is a visualization of flick directions corresponding torespective input IDs in FIG. 57.

FIG. 59 is a diagram that illustrates a correspondence table betweeninput IDs and respective groups in an English character input mode.

FIG. 60 is a diagram that illustrates a correspondence table betweeninput IDs and IDs corresponding to English characters, etc. included inrespective group IDs referenced from the correspondence table in FIG. 59(internal group IDs) during an English character input mode.

FIG. 61 is a diagram that illustrates a correspondence table ofcorrespondences between group IDs in FIG. 59 and respective internalgroup IDs in FIG. 60, as well as respective English characters belongingto each group ID's group in the case where the English character inputmode is an English character keypad-relative input mode.

FIG. 62 is a diagram that illustrates a correspondence table ofcorrespondences between group IDs in FIG. 59 and respective internalgroup IDs in FIG. 60, as well as respective English characters belongingto each group ID's group in the case where the English character inputmode is an English character 4 group-relative input mode.

FIG. 63 is a diagram that illustrates a correspondence table ofcorrespondences between group IDs in FIG. 59 and respective internalgroup IDs in FIG. 60, as well as respective English characters belongingto each group ID's group in the case where the English character inputmode is an English word-relative input mode.

FIG. 64 is a diagram that illustrates a correspondence table betweeninput IDs and respective consonants in a Japanese character input mode.

FIG. 65 is a diagram that illustrates a correspondence table betweeninput IDs and respective vowels in a Japanese character input mode.

FIG. 66 is a diagram that illustrates a correspondence table betweenconsonant IDs and vowel IDs during a Japanese character input mode.

FIG. 67 is a diagram that illustrates a correspondence table betweeninput IDs and respective numerals in a numeral input mode.

FIG. 68 is a diagram that illustrates a correspondence table with theIDs of respective menu groups in the case where menu selection isconducted.

FIG. 69 is a diagram that illustrates a correspondence table betweeninput IDs and IDs corresponding to menu items belonging to respectivegroup IDs referenced from the correspondence table in FIG. 68 (internalgroup IDs) in the case where menu selection is conducted.

FIG. 70 is a diagram that illustrates a correspondence table that givesmenu items during music playback as an example of the respective menuitems corresponding to internal group IDs for menus illustrated in FIG.69.

FIG. 71 is a flowchart that illustrates the flow of a series ofprocesses during information input of characters, etc. in the presentembodiment, and which illustrates the flow up to an ID additionprocessing part after proceeding from a browser view mode to a characterinput mode.

FIG. 72 is a flowchart that illustrates the flow of a series ofprocesses during information input of characters, etc. in the presentembodiment, and which illustrates the process flow after proceeding to aconversion mode of a Japanese character input mode from among thecharacter input modes.

FIG. 73 is a flowchart that illustrates a detailed process flow in theID addition processing part of FIG. 71 in the case where the characterinput mode is an English character input mode.

FIG. 74 is a flowchart that illustrates detailed process flow in the IDaddition processing part of FIG. 71 in the case where the characterinput mode is a Japanese character input mode.

FIG. 75 is a flowchart that illustrates a detailed process flow in theID addition processing part of FIG. 71 in the case where the characterinput mode is a numeral input mode.

FIG. 76 is a flowchart that illustrates a detailed process flow in theID addition processing part of FIG. 71 in the case where the operationalmode is a menu item selection input mode.

FIG. 77 is a flowchart that illustrates a detailed process flow in theID addition processing part of FIG. 71 in the case where the operationalmode is a phone book information search mode.

FIG. 78 is a flowchart that illustrates the flow up to an ID additionprocessing part after proceeding to a character input mode from amongthe process flows during desired information input by consecutive flickgestures.

DESCRIPTION

Hereinafter, an embodiment of the present disclosure will be describedwith reference to the drawings.

(Schematic Configuration of Mobile Information Device)

FIG. 1 illustrates an exemplary schematic internal configuration of amobile information device given as one example of an information inputapparatus of the present embodiment. Herein, the mobile informationdevice of the present embodiment comprises a smartphone, tablet device,etc. provided with a touch panel on top of a display panel, for example.

In FIG. 1, a communication antenna 101 is for example a built-inantenna, which transmits and receives telephony and email, downloadsvarious application programs including an information input controlprogram of the present embodiment, and transmits and receives signalwaves for communicating on the Internet, etc. via a mobile network orpublic wireless communication network. An antenna circuit 102 comprisesan antenna switcher, matching circuit, filter circuit, etc. while atransceiver circuit unit 103 conducts frequency conversion, modulation,demodulation, etc. of outgoing and incoming signals via a mobile phonenetwork or public wireless communication network.

A speaker 115 is a speaker provided in the mobile information device ofthe present embodiment, and is used for music playback, incomingtelephony output, ringer sounds (ringtones), etc. for example. Amicrophone 116 is used for external audio pickup and outgoing telephonyaudio pickup, etc. An audio signal processing unit 114 comprises anamplification circuit for the speaker 115, an amplification circuit forthe microphone 116, a decompression decoding circuit that decompressesand decodes compressed and coded audio data supplied from acontrol-computation unit 104, a digital/analog conversion circuit thatconverts digital audio data after the decompression and decoding into ananalog audio signal, an analog/digital conversion circuit that convertsan analog audio signal input from the microphone 115 into digital audiodata, and a compression coding circuit that compresses and encodes thedigital audio data, etc.

A video signal processing unit 111 comprises a decompression decodingcircuit that decompresses and decodes compressed and coded video datasupplied from the control-computation unit 104, a display panel drivecircuit that causes digital video after the decompression and decodingor digital broadcast video, etc. received at a digital broadcastreception module 109 later described to be displayed on a display panel112. Also, in the case of the present embodiment, the video signalprocessing unit 111 also generates video signals for displaying desktopimages, various menu images, virtual touch area images corresponding topositions on the touch panel, etc. supplied from the control-computationunit 104, and causes such images to be displayed on the display panel112.

A key operation unit 119 comprises physical keys provided on the chassisof the mobile information device of the present embodiment and theirperipheral circuits, etc. The key operation unit 119 converts physicalkey press operation input by the user into an electrical signal,amplifies and analog/digital converts the operation input signal, andsends the analog/digital converted operation input data to thecontrol-computation unit 104.

An external input and output terminal unit 118 comprises one or morecable connection connectors for conducting data communication via acable for example and an interface circuit for external datacommunication, a charge terminal for charging an internal battery via apower cable, etc. and an interface circuit for charging, etc. Variousapplication programs including an information input control program ofthe present embodiment may also be acquired via the external input andoutput terminal unit 118.

Also, an external memory I/F unit 110 comprises a external memory slotinto which a storage medium such as external memory is loaded andunloaded, an interface circuit for data communication with the externalmemory, etc. Various application programs including an information inputcontrol program of the present embodiment may also be acquired via astorage medium such as external memory loaded into the external memoryI/F unit 110. Herein, the storage medium may also be a medium storinginformation such as an information input control application program forcontrolling later-described information input processes of a mobileinformation device of the present embodiment.

A near field wireless communication module 108 comprises a communicationantenna for near field wireless radio waves such as wireless LAN orBluetooth (registered trademark), and a near field wirelesscommunication circuit. Various application programs including aninformation input program of the present embodiment may also be acquiredvia the near field wireless communication module 108.

A digital broadcast reception module 109 comprises an antenna and tunerfor receiving what is called digital television broadcasts and digitalradio broadcasts, etc. The digital broadcast reception module 109 doesnot only receive a digital broadcast on a single channel, but is made tobe capable of receiving digital broadcasts on multiple channelssimultaneously. In addition, the digital broadcast reception module 109is also made to be capable of receiving data multiplexed into a digitalbroadcast. Herein, digital broadcast data received at the digitalbroadcast reception module 109 is also made to be capable of beingstored in a memory unit 105, etc. (in other words recorded) after beingcompressed, etc. by the control-computation unit 104, for example. Also,various application programs including an information input controlprogram of the present embodiment may also be broadcast as one part ofthe display broadcast data.

A camera unit 113 comprises an imaging element for shooting still imagesand moving images, optics, etc. and their peripheral circuits, as wellas a drive circuit for a light for emitting shoot-assistive light. Stillimage data and moving image data during shooting by the camera unit 113is sent to the video signal processing unit 111 as preview video data.In so doing, preview video is displayed on the display panel 112 duringthe camera shooting. Also, in the case of recording still image data ormoving image data shot with the camera unit 113, the shot still imagedata or moving image data is sent to the control-computation unit 104and compressed, and then stored in the memory unit 105 or in externalmemory connected to the external memory I/F unit 110.

A non-contact communication module 107 conducts non-contactcommunication via a non-contact communication antenna, which is used byfor example what is called RFID (Radio Frequency-Identification) andnon-contact type IC cards, etc.

A GPS (Global Positioning System) module 106 includes a GPS antenna, anduses a GPS signal from a GPS positioning satellite to compute thelatitude and longitude of the current positions of the device itself.GPS data (information expressing latitude and longitude) acquired by theGPS module 106 is sent to the control-computation unit 104. In so doing,the control-computation unit 104 is able to ascertain the currentposition and movement of the device itself.

A multi-sensor unit 117 comprises various detection sensors such asdevice state sensors for detecting the state of a mobile informationdevice 1 of the present embodiment, and their peripheral circuits. Tiltsensors, acceleration sensors, orientation sensors, temperature sensors,humidity sensors, illumination sensors, etc. can be given as examples ofthe multi-sensor unit 117. Detection signals from the multi-sensor unit117 are sent to the control-computation unit 104. In so doing, thecontrol-computation unit 104 is able to ascertain the state (tilt,acceleration, orientation, temperature, humidity, illumination, etc.) ofthe mobile information device 1.

A touch panel 121 is an input operation unit that includes a detectionsurface able to detect operation input by the user, and comprises atransparent touch sensor screen sensor distributed over the entiresurface of the display panel 112. A touch panel signal processing unit120 measures the touch detection position, touch trail, continuous touchtime, touch time interval, etc. from the touch panel 121, and deliversthe measured data to the control-computation unit 104 as touch detectiondata. Herein, the touch panel 121 and the touch panel signal processingunit 120 are compatible with what is called multi-touch.

The memory unit 105 comprises internal memory provided inside the deviceand removable card type memory. The removable card type memory may be acard, etc. storing what is called SIM (Subscriber Identity Module)information, etc. The internal memory comprises ROM (Read Only Memory)and RAM (Random Access Memory). The ROM stores an OS (Operating System),control programs whereby the control-computation unit 104 controlsrespective units, various default setting values, dictionary data,character prediction and conversion dictionary data, various sound data,various application programs including an information input controlprogram of the present embodiment, etc. This ROM includes rewritable ROMsuch as NAND-type flash memory or EEPROM (Electrically ErasableProgrammable Read-Only Memory), and is made to be capable of savingemail data, phone book and email address book data, still image andmoving image content data, other data, various user setting values, etc.The RAM is a work area when the control-computation unit 104 conductsvarious data processes, and stores data as needed as a buffer area.

The control-computation unit 104 comprises a CPU (Central ProcessingUnit), controls respective units such as the transceiver circuit unit103, the video signal processing unit 111, the audio signal processingunit 114, the GPS module 106, the non-contact communication module 107,the near field wireless communication module 108, the digital broadcastreception module 109, the external memory I/F unit 110, the camera unit113, the multi-sensor unit 117, the external input and output terminalunit 118, the key operation unit 119, and the touch panel signalprocessing unit 120, and conducts various computations as needed. Also,the control-computation unit 104 executes control programs stored in thememory unit 105 and various application programs including aninformation input control program of the present embodiment.Additionally, in the case of the present embodiment, by executing aninformation input control program, the control-computation unit 104functions as an information assignment control unit that respectivelyassigns given information such as later-described characters to aplurality of directions on a touch panel surface approximately centeredon a user-desired operation input position with respect to the panelsurface. Also, in the case of the present embodiment, by executing aninformation input control program, the control-computation unit 104functions as an information input control unit. When an operation inputdirection given by the user on the touch panel surface approximatelymatches one from the plurality of directions, the information inputcontrol unit inputs the given information assigned to the approximatelymatching direction as user-selected information. Herein, flows ofoperational control by the mobile information device 1 due to thecontrol-computation unit 104 executing a control program or applicationprogram will be discussed later.

Otherwise, a mobile information device of the present embodimentobviously may be also provided with respective component elementstypically provided in a mobile information device, such as a clock unitthat measures the time and elapsed time, a battery that supplies powerto each unit, and a power management IC that controls such power.

(Information Input Using a Touch Panel)

By using the touch panel, a mobile information device of the presentembodiment is configured to enable character and other informationinput, menu operations, information input for phone book, etc.information searches, etc. as described hereinafter.

With an information input technique of the present embodiment, twogesture operations are used: a gesture operation wherein the user tapshis or her finger, etc. on top of the touch panel (hereinafterdesignated a tap gesture); and a gesture operation wherein the userslides his or her finger, etc. that has contacted the top of the touchpanel in a constant given direction while releasing the finger, etc.from the touch panel (hereinafter designated a flick gesture).

In an information input technique of the present embodiment, inputcharacter information is taken to be, for example, English characters,Japanese characters, numerals, symbols, etc. Also, an information inputtechnique of the present embodiment is made to be not only applicable tothe input of character information, but also to, for example,information input for menu selection, information input for searching anaddress book or phone book, etc. Hereinafter, an information inputtechnique of the present embodiment will be described for Englishcharacter input, Japanese character input, numeral input, informationinput for menu selection, and information input for searching an addressbook, etc., in that order.

(Exemplary English Character Input)

In the case of an information input technique of the present embodiment,English character input is made to be realizable by for example one tapgesture and two flick gestures per input of a single character,excluding some exceptions. Details will be discussed later, but in thepresent embodiment, English character input is conducted by selectingthe group in which exists the character that the user wants to inputwith a first flick gesture after a tap gesture, and selecting acharacter included in the group selected by the previous flick gesturewith a second flick gesture, for example.

FIGS. 2 to 17 illustrate a flow of screen transitions and gestureoperations on a touch panel during the English character input. In thedescription hereinafter, an example is given wherein the user inputsdesired English characters as a search keyword (“xmas”, for example)during a web search. However, the present embodiment is obviously notlimited to this example. Also, in the case of this example, thecharacter input mode of a mobile information device of the presentembodiment is taken to be set to an English character input mode.

FIG. 2 illustrates an example wherein a mobile information device of thepresent embodiment is in a browser screen mode, and a browser screenwith a text box 2 and a search button 3 disposed thereon is displayed ona display screen 1.

In this browser screen illustrated in FIG. 2, the text box 2 is an areaprepared for the user to input the characters, etc. of a desired searchkeyword. The search button 3 is a virtual button for the user to inputan instruction for initiating a web search using the search keywordafter the user-desired search keyword characters have been input intothe text box 2. Herein, the exemplary browser screen in FIG. 2 gives anexample wherein a text box 2 and a search button 3 are disposed, butobviously other elements such as a variety of images, a link area forjumping to other websites and webpages, etc. may also be disposed. Inother words, in the browser screen mode, in the case where for examplethe top of the touch panel corresponding to the link area, etc. istapped, etc., by the user, a mobile information device will jump to thelink destination embedded in that link area. As another example, incases where the browser screen size is larger than the display screensize, the user may conduct a gesture of sliding his or her finger whilein a state of contact with the touch panel (hereinafter designated aslide gesture) or a flick gesture, for example. In such cases, a mobileinformation device is also configured to enable scrolling the browserscreen in the slide direction or flick direction given by thosegestures.

In this browser screen illustrated in FIG. 2, if the user for exampletaps a touch panel position corresponding to the text box 2 asillustrated in FIG. 3, for example, then a mobile information device ofthe present embodiment will set the inside of the text box 2 to anactive state, and transition to a state enabling character input of asearch keyword, etc. In the example in FIG. 3, herein, during the tapgesture, a finger contact point 10 is drawn on the figure in order toeasily visualize the position on the display screen (on the touch panel)contacted by the user's finger, etc. In the case of this example, afinger contact point 10 is not something that is for example displayed,etc. on the display screen, but it may displayed on the display screento enable the user to recognize the finger contact position.

Also, as discussed earlier, if an area for character input such as thetext box 2 enters an active state in response to a tap gesture, a mobileinformation device of the present embodiment causes the operational modeof the device itself to transition to a full screen takeover modewherein approximately the entire screen of the touch panel is used forinformation input of characters, etc. At the same time, a mobileinformation device of the present embodiment causes the display of thedisplay screen to transition to a takeover mode screen 1J as illustratedin FIG. 4 for example, in order to enable the user to recognize that theoperational mode of the device itself has transitioned to a full screentakeover mode. Herein, a full screen takeover mode is a mode forpreventing operations other than input operations during characterinput, menu selection, information search, etc. in the presentembodiment. The full screen takeover mode is canceled when a physicalkey separately provided on a mobile information device of the presentembodiment is pressed, or when an end input function is selected in themode.

As illustrated in FIG. 4, the takeover mode screen 1J is made to be ascreen wherein parameters such as the color, brightness, transparency,etc. of the browser screen illustrated in the above FIG. 2 are changedto dedicated full screen takeover mode parameters. Herein, in the caseof the example in FIG. 4, the takeover mode screen 1J is made to be ascreen wherein it appears that a semi-transparent image has beenoverlaid on top of the browser screen illustrated in the above FIG. 2.

Also, as illustrated in FIG. 4, the takeover mode screen 1J is providedwith a current input text display area 11 disposed at a given positionon the screen, and respective function areas 12 to 15 disposed at thefour corners of the screen, for example.

In the present embodiment, the current input text display area 11 ismade to be an area that enlarges and displays characters in the processof being input, a cursor, etc. Meanwhile, in the case where charactersin the process of being input, a cursor, etc. are being displayed in thecurrent input text display area 11, those characters in the process ofbeing input, cursor, etc. are also displayed in the text box 2.

The respective function areas 12 to 15 are areas to which are assignedgiven functions used during the input of characters, etc.

In the case of the present embodiment, the function area 12 disposed atthe upper-left corner of the screen is made to be, for example, an areainstructed when inputting what are called face marks and other suchspecial characters, etc. (hereinafter designated the special characterinstruction area 12 as appropriate). In the case where for example thisspecial character instruction area 12 receives a tap gesture, etc., amobile information device for example switches approximately the entirearea of the touch panel to a special character selection takeover mode,and also displays a list of various special characters such as facemarks, etc. on the screen. Also, when entering a special characterselection takeover mode, a mobile information device is configured suchthat respective special characters in the list can be scrolled by slidegestures and flick gestures, for example, and is additionally configuredsuch that a desired special character in the list can be selected byperforming a tap gesture on that special character. Then, when a desiredspecial character from the list is indicated by the user by means of atap gesture, a mobile information device takes that special character ashaving been selected by the user, and inputs that special character intoa character input area such as the text box 2.

The function area 13 disposed at the upper-right corner of the screen ismade to be an area instructed when for example moving the cursor, etc.(hereinafter designated the cursor instruction area 13 as appropriate).In the case where for example the cursor instruction area 13 receives atap gesture, etc., a mobile information device for example switchesapproximately the entire area of the touch panel to a cursor movementtakeover mode. When entering the cursor movement takeover mode, a mobileinformation device for example causes cursor movement instruction marks,etc., which represent respective directions in which to move the cursorup, down, left, or right, to be displayed on the screen, and alsoswitches the touch panel to input for moving the cursor. Then, when adesired cursor movement instruction mark from among the marks isindicated by for example a tap gesture, etc., a mobile informationdevice moves the cursor in that direction on the screen.

The function area 14 disposed at the lower-left corner of the screen ismade to be an area to which is assigned a convert/symbol selectionfunction used when selecting various symbols used in character input orwhen conducting later-described kana-kanji conversion, etc. (hereinafterdesignated the convert/symbol instruction area 14 as appropriate).Herein, in cases such as when a character input mode is alater-described Japanese character input mode, a conversion function forJapanese kana-kanji conversion is assigned to the convert/symbolinstruction area 14. In the case where the convert/symbol instructionarea 14 for example receives a tap gesture, etc., a mobile informationdevice for example switches approximately the entire area of the touchpanel to a symbol selection takeover mode, and also displays a list ofvarious symbols on the screen. Also, when entering a symbol selectiontakeover mode, a mobile information device is configured such thatrespective symbols in the list can be scrolled by slide gestures andflick gestures, for example, and is additionally configured such that adesired symbol in the list can be selected by performing a tap gestureon that symbol. Then, when a desired symbol from the list is indicatedby the user by means of a tap gesture, a mobile information device takesthat symbol as having been selected by the user, and inputs that symbolinto a character input area such as the text box 2. Meanwhile, thekana-kanji conversion function of the convert/symbol instruction area 14during a Japanese character input mode will be discussed later.

The function area 15 disposed at the lower-right corner of the screen ismade to be for example an area instructed when inputting a backspace(hereinafter designated the backspace input area 15 as appropriate).When the backspace input area 15 is instructed by for example a tapgesture, etc., a mobile information device for example backs up thecursor in a character input area by one character, while also deletingthat character.

Also, in the case of transitioning to the full screen takeover mode, amobile information device temporarily suspends functions that whereactive during the browser screen mode, for example. In other words, inthe case of transitioning to a full screen takeover mode, even if aposition on the touch panel corresponding to a link area, etc. of thebrowser screen is tapped, etc., a mobile information device will notjump, etc. to the link destination given by the link area, and willinstead maintain the full screen takeover mode. Similarly, in the caseof transitioning to a full screen takeover mode, even if the userperforms a slide gesture or flick gesture for the purpose of screenscrolling as described earlier, a mobile information device will notscroll the browser screen, and will instead maintain the full screentakeover mode.

Then, when the user's finger contacts a desired position on the touchpanel as illustrated in FIG. 5 for example while in a state wherein atakeover mode screen 1J is being displayed due to transitioning to thefull screen takeover mode, a mobile information device of the presentembodiment causes a group object group 20 as illustrated in FIG. 6 to bedisplayed on the takeover mode screen 1J. Herein, in the examples inFIG. 5 and FIG. 6, a finger contact point 10 is drawn on the figures inorder to easily visualize the position on the touch panel contacted bythe user's finger, etc., similarly to the example in the above FIG. 3.Similarly to that discussed earlier, the finger contact point 10 is notsomething that is for example displayed, etc. on the display screen inpractice, but obviously it may also be displayed on the display screen.

In the present embodiment, the group object group 20 illustrated in FIG.6 is a group of objects corresponding to respective groups disposed onthe basis of what is called a keypad layout, for example. The groupobject positioned at the center of the keypad layout is positioned tocorrespond with the position of the finger contact point 10. Also, inthe group object group 20, arrow objects are drawn from the group objectat the finger contact point 10 position (in other words the center ofthe keypad layout) to the other respective group objects. The arrowdirections of these respective arrow objects are made to be indicatorsfor informing the user of a flick direction when performing a flickgesture from the finger contact point 10 position (the center of thekeypad layout). Meanwhile, in the description hereinafter, an Englishcharacter input mode wherein respective group objects are approximatelyassociated with a keypad layout, or in other words, an English characterinput mode wherein the flick directions of flick gestures areapproximately associated with a keypad layout, will be designated theEnglish character keypad-relative input mode as appropriate.

In the present embodiment, each group object belonging to the groupobject group 20 is respectively associated with an alphabetic charactergroup during English character input by what is called a keypad layout.In other words, as one example, in the case of English character input,a character group with the alphabetic characters “jkl” is assigned tothe group object corresponding to the finger contact point 10 (in otherwords the group object positioned at the center of the keypad layout).Also, a character group with the alphabetic characters “abc” is assignedto the group object disposed at a given position on the screen and inthe vicinity of the finger contact point 10, such as in the upwarddirection, for example. Similarly, a character group “def” is assignedto a group object disposed at a given position approximately 45 degreesupward and to the right in the vicinity of the finger contact point 10,a character group “ghi” is assigned to a group object disposed at agiven position in the right horizontal direction in the vicinity of thefinger contact point 10, a character group “mno” is assigned to a groupobject disposed at a given position in the left horizontal direction inthe vicinity of the finger contact point 10, a character group “pqrs” isassigned to a group object disposed at a given position approximately 45degrees downward and to the left in the vicinity of the finger contactpoint 10, a character group “tuv” is assigned to a group object disposedat a given position in the downward direction in the vicinity of thefinger contact point 10, and a character group “wxyz” is assigned to agroup object disposed at a given position approximately 45 degreesdownward and to the right in the vicinity of the finger contact point10.

Meanwhile, in the case of this example, since the number of groups intowhich the 26 characters of the alphabet are divided is made to be 8groups, character groups are not assigned to all 9 group objects of thekeypad layout, and an assignment like that illustrated in FIG. 6 isconfigured as one example. Obviously, a character group may also beassigned to for example the group object approximately 45 degrees upwardand to the left of the finger contact point 10. Also, it is alsopossible to separately assign for example a user-desired character groupor symbol group as function information, or other functions, etc. to agroup object that is not assigned with a character group in advance inthis way. Besides the above, a mobile information device of the presentembodiment is configured to enable the assignment of character groups,etc. even for the group objects assigned with character groups inadvance to be appropriately changed to other character groups and symbolgroups, or to other functions.

Also, although the example in FIG. 6 illustrates how a group objectgroup 20 is displayed on a takeover mode screen 1J, the group objectgroup 20 may also not be displayed in cases such as when the user hasmemorized the positional relationships of the respective group objectsand the assignments between each group object and alphabetic charactergroup, for example. Also, in the present embodiment, the display andnon-display of the group object group 20 may also be appropriatelyswitched according to an arbitrary setting by the user, for example.

Next, if the user performs a flick gesture toward the disposed directionof a desired character group while in a state wherein respectivecharacter groups are assigned on the basis of a keypad layout that takesthe finger contact point 10 as illustrated in the above FIG. 5 as thecenter position, a mobile information device of the present embodimentdetermines that the character group in the direction of that flickgesture has been selected by the user. As in the present embodiment,given an example wherein the characters “xmas” are input, when thecharacter “x” is input, the flick gesture direction becomesapproximately 45 degrees downward and to the right from the fingercontact point 10 as illustrated in FIG. 7. In so doing, the charactergroup “wxyz” is selected as illustrated in FIG. 8. Meanwhile, in thepresent embodiment, the selection of a character group assigned to thegroup object corresponding to the finger contact point 10 is executed inthe case where a tap gesture is performed, such as when the user touchesthe top of the touch panel corresponding to the group object with his orher finger, and then releases his or her finger, etc. from the touchpanel as-is without flicking, etc. Also, in the example in FIG. 7, andsimilarly to the example in the above FIG. 6, the finger contact point10 a is a point drawn on the figure in order to visualize the contactposition of the finger during a tap gesture, and the arrow extendingfrom the finger contact point 10 a to the finger contact point 10 b isan arrow drawn in order to visualize the flick direction of the flickgesture. Also, the broken lines enclosing an arrow object in FIG. 8 arelines drawn in order to visualize the direction input from the user bythe flick gesture. The finger contact points 10 a and 10 b, the arrowextending from the finger contact point 10 a to the finger contact point10 b, and the broken lines enclosing an arrow object are not somethingthat is for example displayed, etc. on the display screen, but they mayalso be displayed on the display screen to enable the user to recognizethem.

If a user-desired character group is selected as in the above FIG. 7 andFIG. 8, a mobile information device of the present embodiment goes backto a takeover mode screen 1J similar to FIG. 4 as illustrated in FIG. 9,and in a state wherein the character group selected by the user isremembered. This takeover mode screen 1J illustrated in FIG. 9 becomes astandby state with respect to a second flick gesture.

Then, if for example the user contacts his or her finger, etc. with adesired position on the touch panel as illustrated in FIG. 10 while in astate wherein a character group selected by the user is beingremembered, a mobile information device of the present embodiment causesa character object group 21 as illustrated in FIG. 11 to be displayed onthe takeover mode screen 1J. Herein, in the examples in FIG. 10 and FIG.11, and similarly to that discussed earlier, a finger contact point 10is drawn in order to visualize the contact position of the user'sfinger, etc. In this case, similarly to that discussed earlier, thefinger contact point 10 is not something that is displayed, etc. on thedisplay screen, but obviously it may also be displayed on the displayscreen.

In the present embodiment, the character object group 21 illustrated inFIG. 11 is a group of objects corresponding to respective charactersbelonging to the previously selected character group and disposed on thebasis of a keypad layout similar to that discussed earlier. The objectpositioned at the center of the keypad layout is positioned incorrespondence with the position of the finger contact point 10. Also,in the character object group 21, arrow objects are drawn from thecharacter object at the finger contact point 10 position (the center ofthe keypad layout) to the other respective character objects. The arrowdirections of these respective arrow objects are made to be indicatorsfor informing the user of a flick direction when performing a flickgesture from the finger contact point 10 position (the center of thekeypad layout).

In the present embodiment, each character object belonging to thecharacter object group 21 is respectively associated with a respectivealphabetic character belonging to a previously selected character group.In other words, in the case of this example, since the previouslyselected character group is the above “wxyz”, the alphabetic character“w” is assigned to a character object disposed at a given position onthe screen and in the vicinity of the finger contact point 10, such asin the upward direction, for example. Similarly, the character “z” isassigned to a character object disposed at a given position in the righthorizontal direction in the vicinity of the finger contact point 10, thecharacter “x” is assigned to a character object disposed at a givenposition in the left horizontal direction in the vicinity of the fingercontact point 10, and the character “y” is assigned to a characterobject disposed at a given position in the downward direction in thevicinity of the finger contact point 10.

Meanwhile, in the case of this example, since the number of charactersbelonging to the previously selected character group 4 characters,characters are not assigned to all 9 character objects of the keypadlayout, and instead characters are assigned to the four characterobjects up, down, left, and right with respect to the finger contactpoint 10 as one example. Obviously, the 4 characters may also beassigned to for example the four character groups approximately 45degrees upward and to the left, approximately 45 degrees upward and tothe right, approximately 45 degrees downward and to the left, andapproximately 45 degrees downward and to the right, or additionally toother character objects. A character may also be assigned to thecharacter object corresponding to the finger contact point 10. In casessuch as when a character is assigned to the character objectcorresponding to the finger contact point 10, the character assigned tothe character object corresponding to the finger contact point 10 isselected when a tap gesture is performed while in a state wherein acharacter group selected by the user is remembered, wherein the usertouches a desired position on the touch panel with his or her finger,etc., and then directly releases his or her finger, etc. from the touchpanel. In addition, it is also made possible to separately assign forexample user-desired characters or symbols as function information, orother functions, etc. to respectively group objects that are notassigned with a character, etc. in advance. Furthermore, it is also madepossible to appropriately change the assignment of characters, etc. evenfor the character objects assigned with characters, etc. in advance toother characters and symbols, or to other functions.

Also, although the example in FIG. 11 illustrates how a character objectgroup 21 is displayed on a takeover mode screen 1J, the character objectgroup 21 may also not be displayed in cases such as when the user hasmostly memorized the positional relationships of the respectivecharacter objects and the assignments between each character object andeach character, for example. Also, in the present embodiment, thedisplay and non-display of the character object group 21 may also beappropriately switched according to an arbitrary setting by the user,for example.

Next, if for example the user performs a flick gesture toward thedisposed direction of a desired character while in a state whereinrespective characters are assigned on the basis of a keypad layout thattakes the finger contact point 10 as illustrated in FIG. 10 discussedearlier as the center position, a mobile information device of thepresent embodiment determines that the character in the direction ofthat flick gesture has been selected by the user. As in the presentembodiment, in the case of an example of inputting into the text box 2the character “x” from “xmas” as the search keyword, the flick gesturedirection becomes the right horizontal direction from the finger contactpoint 10 as illustrated in FIG. 12. In so doing, the character “x” isselected as illustrated in FIG. 13. Meanwhile, similarly to thatdiscussed earlier, the finger contact point 10 a is a point drawn inorder to visualize the contact position of the finger during a tapgesture, and the arrow extending from the finger contact point 10 a tothe finger contact point 10 b is an arrow drawn in order to visualizethe flick direction. Also, the broken lines enclosing an arrow object inFIG. 13 are lines drawn in order to visualize the direction input by theuser by the flick gesture. The finger contact points 10 a and 10 b, thearrow linking them, and the broken lines enclosing an arrow object arenot something that is for example displayed, etc. on the display screen,but they may also be displayed on the display screen to enable the userto recognize them.

In so doing, if for example the character “x” is selected, a mobileinformation device of the present embodiment displays the character “x”followed by a cursor in the current input text display area 11, and alsosimilarly displays the character “x” followed by a cursor in the textbox 2, as illustrated in FIG. 14.

Among the characters in “xmas” input as the search keyword, input isconducted similarly to that discussed above for the respectivecharacters “m”, “a”, and “s” following the above “x”. FIG. 15illustrates the state wherein the characters up to “xm” from thecharacters in “xmas” have been input. FIG. 16 illustrates a statewherein the input of all the characters in “xmas” has finished.

After the input of all user-desired characters has finished asillustrated in the above FIG. 16, if the user performs a press operationon a key from among the physical keys provided on the key operation unit119 discussed earlier that is provided with a “Back” function forreturning the device mode, etc. to a previous state, then a mobileinformation device of the present embodiment cancels the full screentakeover mode, and transitions to a browser screen mode like thatillustrated in FIG. 17. The browser screen mode in FIG. 17 is in a statewherein the input of the characters “xmas” in the text box 2 hascompleted. Consequently, if for example the search button 3 receives atap gesture, etc. while in this state, a mobile information device ofthe present embodiment executes a web search, etc. in the browserscreen, taking the above “xmas” as the search keyword.

Meanwhile, if a touch panel position corresponding to the text box 2receives a tap gesture similarly to FIG. 3 as discussed earlier while inthe browser screen mode in FIG. 17, a mobile information device of thepresent embodiment transitions to a full screen takeover mode similar tothat discussed earlier, and enters a state enabling further characters,etc. to be added starting at a cursor position following the characters“xmas” in the text box 2. Also, movement of the cursor position in thetext box 2 is made to be capable of being instructed by a tap gesture onthe cursor instruction area 13 discussed earlier followed by a flickgesture, etc. Also, in the present embodiment, operations for backing upthe cursor by one character while also deleting that character, forexample, are made to be capable of being instructed by a tap gestureoperation on the backspace input area 15 discussed earlier.

A more detailed description of the case wherein a mobile informationdevice of the present embodiment executes an English character inputprocess by means of an English character keypad-relative input mode asdiscussed above will be given later.

Also, in the present embodiment, besides an English characterkeypad-relative input mode wherein flick gesture directions areapproximately associated with a keypad layout as discussed earlier,English character input may also be for example an English character 4group-relative input mode or an English word-relative input mode asfollows.

The English character 4 group-relative input mode is an Englishcharacter input mode wherein the respective characters of the alphabetare divided into 4 groups, with both flick gesture directions as well asfour group objects being associated with these 4 groups. A group “a, b,c, d, e, f g”, a group “h, i j, k, 1, m, n”, a group “o, p, q, r, s, t,u” and a group “v, w, x, y, z” can be given as one example of the 4groups. Also, the 4 directions up, down, left, and right from the fingercontact point 10 or the direction 45 degrees upward and diagonally leftdegrees, the direction 45 degrees upward and diagonally right, thedirection 45 degrees downward and diagonally left, and the direction 45degrees downward and diagonally right, for example, are conceivable asthe flick gesture directions in this example. Obviously, these flickgesture directions are an example, and other directions may be used, andit is also possible for the user to arbitrarily set directions. A moredetailed description of the case wherein a mobile information device ofthe present embodiment executes an English character input process bymeans of the English character 4 group-relative input mode will be givenlater.

The English word-relative input mode is an English character input modewherein for example a plurality of meaningful English words consistingof 4 characters are used, with both flick gesture directions as well asgroup objects being respectively associated with each of these Englishwords. The 8 words “bang”, “chip”, “desk”, “from”, “july”, “wave”,“taxy”, “quiz” can be given as one example of the 4 character Englishwords. All 26 characters of the alphabet are included in these Englishwords. Also, an association based on for example the keypad layoutdiscussed earlier can be given as an association between each of thesewords and the flick gesture directions. Herein, a more detaileddescription of the case wherein a mobile information device of thepresent embodiment executes an English character input process by meansof the English word-relative input mode will be given later.

(Exemplary Japanese Character Input)

In the case of an information input technique of the present embodiment,Japanese character input is realized by for example one tap gesture andtwo flick gestures per character, excluding some exceptions. Detailswill be discussed later, but in the present embodiment, Japanesecharacter input is conducted by for example selecting a “row” groupdesired for input with a first flick gesture after a tap gesture, andselecting a “column” character included in the “row” group selected bythe previous flick gesture with a second flick gesture. In other words,with Japanese character input, the “consonant” of a character desiredfor input is selected by a first flick gesture, and the “vowel” of thecharacter desired for input is selected by a second flick gesture. In sodoing, the hiragana character obtained from the combination of this“consonant” and “vowel” is determined. Herein, since in Japanesecharacters there exist characters including what are called smallcharacters such as the small “ya”, small “yu”, and small “yo”, and thedakuten, etc., the present embodiment is configured such that flickgestures corresponding to these small characters and the dakuten, etc.can be set.

FIGS. 18 to 35 illustrate a flow of screen transitions and gestureoperations on a touch panel during Japanese character input. In thedescription hereinafter, an example is given wherein the user inputs adesired character string as a search keyword (“KENSAKU suru”, forexample) during a web search. However, the present embodiment isobviously not limited to the example of this embodiment. Also, in thecase of this example, the character input mode of a mobile informationdevice of the present embodiment is taken to be set to a Japanesecharacter input mode.

The browser screen in which are disposed a text box 2 where a searchkeyword is input and a search button 3, and the state untiltransitioning to a full screen takeover mode by performing a tap gestureon the text box 2 in that browser screen, are the same as FIG. 2 andFIG. 3 discussed earlier.

If the user's finger, etc. touches a desired position on the touch panelas illustrated in FIG. 18 for example after transitioning to the fullscreen takeover mode, a mobile information device causes a group objectgroup 22 as illustrated in FIG. 19 to be displayed on the takeover modescreen 1J. Herein, the finger contact point 10 in FIG. 18 and FIG. 19 issimilar to that discussed earlier.

In the present embodiment, the group object group 22 illustrated in FIG.19 is a group of objects corresponding to respective character groupsdisposed on the basis of what is called a keypad layout, for example,similar to that discussed earlier. The group object positioned at thecenter of the keypad layout is positioned to correspond with theposition of the finger contact point 10.

In the case of Japanese character input as in the present embodiment,each group object belonging to the group object group 22 is respectivelyassociated with a hiragana character group during Japanese characterinput by what is called a keypad layout. In other words, in the case ofa Japanese character input mode, a character group that includes theconsonant “n”, or in other words a character group of the respectivehiragana characters “na ni nu ne no” belonging to the “na row” of thehiragana gojuon syllabary, is assigned to the group object correspondingto the finger contact point 10 (the group object positioned at thecenter of the keypad layout). Also, a character group that includes theconsonant “a”, or in other words a character group of the respectivehiragana characters “a i u e o” belonging to the “a row” of the hiraganagojuon syllabary, is assigned to a group object disposed at a givenposition on the screen and in the vicinity of the finger contact point10, such as approximately 45 degrees upward and to the left, forexample. Similarly, a character group that includes the consonant “k”,or in other words a character group of the “ka row”, is assigned to agroup object disposed at a given position in the upward direction in thevicinity of the finger contact point 10. A character group that includesthe consonant “s”, or in other words a character group of the “sa row”,is assigned to a group object disposed at a given position approximately45 degrees upward and to the right in the vicinity of the finger contactpoint 10. A character group that includes the consonant “t”, or in otherwords a character group of the “ta row”, is assigned to a group objectdisposed at a given position in the left horizontal direction in thevicinity of the finger contact point 10. A character group that includesthe consonant “h”, or in other words a character group of the “ha row”,is assigned to a group object disposed at a given position in the righthorizontal direction in the vicinity of the finger contact point 10. Acharacter group that includes the consonant “m”, or in other words acharacter group of the “ma row”, is assigned to a group object disposedat a given position approximately 45 degrees downward and to the left inthe vicinity of the finger contact point 10. A character group thatincludes the consonant “y”, or in other words a character group of the“ya row”, is assigned to a group object disposed at a given position inthe downward direction in the vicinity of the finger contact point 10. Acharacter group that includes the consonant “r”, or in other words acharacter group of the “ra row”, is assigned to a group object disposedat a given position approximately 45 degrees downward and to the rightin the vicinity of the finger contact point 10. Additionally, acharacter group that includes the consonant “w”, or in other words acharacter group of the “wa row”, is assigned to a group object disposedat a given position farther in the downward direction than the groupobject corresponding to the character group of the consonant “r”. Also,in the case of the Japanese character input mode, an embellish functionused when making a character smaller, for example, is assigned to agroup object in the group object group 22 disposed at a given positionfarther in the left horizontal direction than the group objectcorresponding to the character group that includes the consonant “t”.Furthermore, an embellish function used when applying the dakuten, etc.to a character, for example, is assigned to a group object disposed at agiven position farther in the right horizontal direction than the groupobject corresponding to the character group of the consonant “h”.Herein, the assignments between each of these group objects and theircharacter groups are configured such that the user can alsoappropriately change them. Also, it is configured such that theinformation assigned to respective group objects can be appropriatelychanged to symbols or other functions, etc. instead of just characters.

Also, in the group object group 22 in the case of a Japanese characterinput mode, arrow objects are drawn from the group object at the fingercontact point 10 position (the center of the keypad layout) to the otherrespective group objects. The arrow directions of these respective arrowobjects are made to be indicators for informing the user of a flickdirection when performing a flick gesture from the finger contact point10 position (the center of the keypad layout). However, in the groupobject group 22 in the case of the Japanese character input mode, thereare arrow objects pointing to group objects group objects disposed at apositioned separated from the finger contact point 10 by for example theequivalent of one group object, such as the group object for theconsonant “w” and the group objects to which are assigned the smallcharacter, and dakuten, etc. embellish functions, for example. For thesearrow objects, there are drawn given arrow objects that are made to beindicators for informing the user of a flick direction when performing aflick gesture, while simultaneously informing the user that the flickspeed should be fast.

Although the example in FIG. 19 illustrates how a group object group 22is displayed on a takeover mode screen 1J, the group object group 22 mayalso not be displayed in cases such as when the user has mostlymemorized the positional relationships of the respective group objectsand the assignments between each group object and each character groupcorresponding to respective consonants, for example. Also, in thepresent embodiment, the display and non-display of the group objectgroup 22 may also be appropriately switched according to an arbitrarysetting by the user, for example.

Next, if the user performs a flick gesture toward the disposed directionof a desired character group while in a state wherein respectivecharacter groups are assigned as illustrated in FIG. 18 discussedearlier, a mobile information device of the present embodimentdetermines that the character group in the direction of that flickgesture has been selected by the user. As in the present embodiment, inthe case of an example wherein the user inputs the characters “KENSAKUsum” into the text box 2 as a search keyword, the direction of the flickgesture performed first becomes a direction so as to select thecharacter group of the consonant “k” that includes the character “ke” inthe hiragana reading “kensaku” of “KENSAKU”. For this reason, the firstflick gesture direction when inputting the characters “KENSAKU” is madeto be the direction in which is disposed the character group of theconsonant “k”, or in other words the upward direction from the fingercontact point 10, as illustrated by the example in FIG. 20. In so doing,the character group of the consonant “k” is selected as illustrated inFIG. 21. Herein, the finger contact point 10 a and the finger contactpoint 10 b in FIG. 20, the arrow linking them, the broken linesenclosing an arrow object, etc. are similar to that discussed earlier.

If a user-desired character group is selected as in the above FIG. 20and FIG. 21, a mobile information device of the present embodiment goesback to a takeover mode screen 1J as illustrated in FIG. 22, and in astate wherein the character group selected by the user is remembered. Inthe case of the example in FIG. 22, since the consonant “k” has entereda selected state, the single character “k” followed by a cursor isdisplayed in the current input text display area 11, and similarly, thesingle character “k” followed by a cursor is also displayed in the textbox 2.

Then, if the user's finger, etc. touches a desired position on the touchpanel while in a state wherein the character group selected by the useris remembered, a mobile information device of the present embodimentcauses a character object group 23 as illustrated in FIG. 23 to bedisplayed on the takeover mode screen 1J. Herein, in the example in FIG.23, and similarly to that discussed earlier, a finger contact point 10is drawn in order to visualize the contact position of the user'sfinger, etc.

In the case of this Japanese character input, the character object group23 illustrated in FIG. 23 is a group of objects corresponding torespective characters belonging to a previously selected character groupand disposed on the basis of a keypad layout similar to that discussedearlier. The object positioned at the center of the keypad layout ispositioned so as to correspond with the position of the finger contactpoint 10. Also, in the character object group 23, arrow objects similarto that discussed earlier are drawn from the character object at thefinger contact point 10 position (the center of the keypad layout) tothe other respective character objects. Similarly to that discussedearlier, the arrow directions of these respective arrow objects are madeto be indicators for informing the user of a flick direction whenperforming a flick gesture from the finger contact point 10 position(the center of the keypad layout).

In the present embodiment, the respective character object belonging tothe character object group 23 are disposed on the basis of a keypadlayout while in a state of being respectively associated with respectivehiragana characters obtained by combining the consonant “k” of thepreviously selected character group with respective vowels. In otherwords, in the case of this example, since the previously selectedcharacter group is the above consonant “k”, character objects for therespective hiragana characters “ka”, “ki”, “ku”, “ke”, and “ko” obtainedby means of the consonant “k” and the respective vowels “a”, “i”, “u”,“e” and “o” are disposed on the basis of the keypad layout. For example,the character “ka” obtained from the consonant “k” and the vowel “a” isassigned to a character object disposed at a given position on thescreen and in the vicinity of the finger contact point 10, such as inthe upward direction, for example. Similarly, the character “ki”obtained from the consonant “k” and the vowel “i” is assigned to acharacter object disposed at a given position approximately 45 degreesupward and to the right in the vicinity of the finger contact point 10.The character “ku” obtained from the consonant “k” and the vowel “u” isassigned to a character object disposed at a given position in the righthorizontal direction in the vicinity of the finger contact point 10. Thecharacter “ke” obtained from the consonant “k” and the vowel “e” isassigned to a character object disposed at a given positionapproximately 45 degrees downward and to the right in the vicinity ofthe finger contact point 10. The character “ko” obtained from theconsonant “k” and the vowel “o” is assigned to a character objectdisposed at a given position in the downward direction in the vicinityof the finger contact point 10. Meanwhile, yoon characters (“small ya,small yu, small yo”, etc.) usable with the character group of theconsonant “k” are assigned to a character object disposed at a givenposition in the left horizontal direction in the vicinity of the fingercontact point 10. Consequently, in the case where for example a flickgesture is performed in the left horizontal direction in the vicinity ofthe finger contact point 10 after the character group of the consonant“k” is selected by the user, a mobile information device of the presentembodiment determines that the characters “kya”, “kyu”, “kyo” have beenselected by the user. Herein, the 5 vowels “a”, “i”, “u”, “e”, and “o”used in Japanese character input are assigned to respective characterobjects as in FIG. 23 as an example, but obviously these assignments arean example, and the assignments may be changed as discussed earlier, andother characters and symbols, other symbols, etc. may also be assignedas function information.

Also, although the example in FIG. 23 illustrates how a character objectgroup 23 is displayed on a takeover mode screen 1J, the character objectgroup 23 may also not be displayed in cases such as when the user hasmostly memorized the positional relationships of the respectivecharacter objects and the assignments between each character object andeach character, for example. Also, in the present embodiment, thedisplay and non-display of the character object group 23 may also beappropriately switched according to an arbitrary setting by the user,for example.

Next, if for example the user performs a flick gesture toward thedisposed direction of a desired character while in a state whereinrespective characters are assigned to respective character objects inthe character object group 23 as illustrated in the above FIG. 23, amobile information device of the present embodiment determines that thecharacter in the direction of that flick gesture has been selected bythe user. As in the present embodiment, in the case of an examplewherein the user inputs into the text box 2 the characters “KENSAKUsuru” as the search keyword, the character group of the vowel “e”included in “ke” from the hiragana reading “kensaku” will be selected.For this reason, the flick gesture direction becomes approximately 45degrees downward and to the right from the finger contact point 10 asillustrated in FIG. 24, and as a result the character “ke” is selectedas illustrated in FIG. 25. Meanwhile, the finger contact points 10 a, 10b, etc. in FIG. 23 are similar to that discussed earlier, and inaddition, the broken lines enclosing an arrow object in FIG. 24 aresimilar to that discussed earlier.

In so doing, if for example the character “ke” is selected, a mobileinformation device of the present embodiment displays the character “ke”followed by a cursor in a current input text display area 11, and alsosimilarly displays the character “ke” followed by a cursor in a text box2, as illustrated in FIG. 26.

Among the characters in the hiragana reading “kensaku” of “KENSAKU”input as the search keyword, input is conducted similarly to thatdiscussed above for the respective characters “n”, “sa”, and “ku”following the above “ke”. FIG. 27 illustrates a state wherein the inputof all the characters in “kensaku” has finished.

Next, although the above-discussed hiragana reading “kensaku” may bedirectly used as a search keyword, a mobile information device of thepresent embodiment is also capable of converting that hiragana “kensaku”into the kanji “KENSAKU”.

In the present embodiment, kana-kanji conversion is configured to beexecutable via a tap gesture on a convert/symbol instruction area 14disposed at the lower-left corner of the takeover mode screen 1J. FIG.28 illustrates how a tap gesture is conducted on the convert/symbolinstruction area 14. Herein, the finger contact point 10 in the drawingis similar to that discussed earlier.

In the case where a mobile information device has entered a Japanesecharacter input mode, the convert/symbol instruction area 14 hasconversion functions for Japanese kana-kanji conversion. In the casewhere for example the convert/symbol instruction area 14 receives a tapgesture, etc., a mobile information device switches approximately theentire area of the touch panel to a symbol selection takeover mode asdiscussed earlier. (In the case of Japanese character input, thisbecomes a kana-kanji conversion takeover mode.)

Then, when transitioning to the kana-kanji conversion takeover mode, amobile information device of the present embodiment transitions to akana-kanji conversion takeover screen 1Ja wherein there is displayed onthe display screen a conversion kanji candidate list 30 corresponding tothe hiragana string input into the text box 2, as illustrated in FIG.29.

Also, a mobile information device is at this time configured to enablescrolling respective conversion kanji candidates in the conversion kanjicandidate list by for example slide gestures or flick gestures, and isadditionally configured to enable selection of a desired conversionkanji candidate in that list by a tap gesture.

Herein, in the case of a kana-kanji conversion takeover mode, scrollinstructions for respective conversion kanji candidates in theconversion kanji candidate list are for example configured to berealizable by slide gestures or flick gestures as illustrated in FIG.30. In other words, in the case of this example, a conversion kanjicandidate list is being displayed in a state wherein respectiveconversion kanji candidates are for example disposed vertically on akana-kanji conversion takeover screen 1Ja. Then, in the case where forexample a flick gesture is made in the direction of a finger contactpoint 10 b from a finger contact point 10 a as in FIG. 30, a mobileinformation device of the present embodiment scrolls the respectiveconversion kanji candidates in the upward direction on the screen.Obviously, in the case where a flick gesture is made in the oppositedirection, the respective conversion kanji candidates scroll in thedownward direction on the screen 1Ja. Herein, FIG. 31 illustrates anexample after respective conversion kanji candidates have been scrolledby the flick gesture of the example in FIG. 30.

Also, a mobile information device of the present embodiment disposeswithin the kana-kanji conversion takeover screen 1Ja a character countreduction object 31 as an object for the user to issue instructions foradjusting the character count in the case where the readings ofconversion candidates in the conversion kanji candidate list differ froma desired characters count. Consequently, a mobile information device ofthe present embodiment adjusts the conversion character count in thecase where the character count reduction object 31 receives a tapgesture from the user because the readings of conversion candidates inthe conversion kanji candidate list differ from a desired charactercount. Also, a mobile information device of the present embodimentdisposes within the kana-kanji conversion takeover screen 1Ja an objectwith the characters “Back” displayed thereon as an object for the userto issue instructions for going back to the takeover mode screen 1J inthe case where an insufficiency in the input characters, etc. occurs.Consequently, a mobile information device of the present embodiment goesback to the full screen takeover mode 1J in the case where the objectwith the characters “Back” displayed thereon receives a tap gesture fromthe user.

Also, in the present embodiment, the conversion kanji candidate list isconfigured such that for example a conversion kanji candidatecorresponding to a given position in the screen 1Ja is distinguishablefrom other candidates by a different size and color, or by having agiven mark, etc. attached thereto. In the case where the conversionkanji candidate displayed at the given position is changed due to theabove scrolling being performed, that conversion kanji candidate is madeto be distinguishable from other candidates. Herein, the approximatecenter position of the screen, etc. can be given as an example of thegiven position, but obviously another position may be used, and inaddition, the position may be appropriately changed by the user. Aconversion kanji candidate being displayed at the given positionindicates that it has become a selectable candidate at that time.

Then, in the case where for example the user's finger contacts aposition on the touch panel corresponding to a conversion kanjicandidate being displayed at the given position as illustrated in FIG.33, and additionally where for example a flick gesture is conducted in adirection cutting across that conversion kanji candidate, a mobileinformation device of the present embodiment determines that thatconversion kanji candidate has been selected by the user. Herein, thefinger contact points 10, 10 a, 10 b, and the arrow pointing from thefinger contact point 10 to 10 b in FIG. 32 and FIG. 33 are similar tothat discussed earlier.

If a conversion kanji candidate is selected by the user as discussedabove, a mobile information device inputs that selected conversion kanjicandidate into the current input text display area 11 and text box 2 asa kanji conversion of the hiragana characters, as illustrated in FIG.34. Also, a mobile information device at this time goes back to the fullscreen takeover mode 1J.

After the input of the characters “KENSAKU” is finished, the characters“suru” are input similarly to that discussed earlier. In so doing, thecharacters “KENSAKU suru” are input into a current input text displayarea 11 and a text box 2, as illustrated in FIG. 35.

After the input of all user-desired characters has finished asillustrated in the above FIG. 35, if the user performs a press operationon a physical “Back” key of the key operation unit 119, then a mobileinformation device of the present embodiment cancels the full screentakeover mode, and transitions to a browser screen mode. The browserscreen mode at this time is in a state wherein the input of thecharacters “KENSAKU suru” into the text box 2 has completed.Consequently, if for example the search button 3 receives a tap gesture,etc. while in this state, a mobile information device of the presentembodiment executes a web search, etc. in the browser screen, taking theabove “KENSAKU suru” as the search keyword.

A detailed process flow for realizing Japanese character input asdiscussed above in a mobile information device of the present embodimentwill be given later.

(Exemplary Numeral Input)

In the case of an information input technique of the present embodiment,numeral input is realized by for example one tap gesture and one flickgesture per numeral.

Herein, an example will be described for inputting numerals into a textbox 2 as discussed earlier.

If the user's finger, etc. touches a desired position on the touch panelafter transitioning to a full screen takeover mode as discussed earlierin the case where the character input mode is configured to be a numeralinput mode, a mobile information device causes a numeral object group 24to be displayed on the takeover mode screen 1J as illustrated in FIG.36. Herein, the finger contact point 10 in FIG. 36 is similar to thatdiscussed earlier.

In the present embodiment, the numeral object group 24 illustrated inFIG. 36 is a group of objects corresponding to the respective numerals“1”, “2”, “3”, “4”, “5”, “6”, “7”, “8”, “9”, “0”, and for example thetwo symbols “*” and “#” (these are collectively designated numeralobjects), which are disposed on the basis of what is called a keypadlayout, for example. The group object positioned at the center of thekeypad layout is positioned to correspond with the position of thefinger contact point 10. Also, in the numeral object group 24, arrowobjects similar to that discussed earlier are drawn from the characterobject at the finger contact point 10 position (the center of the keypadlayout) to the other respective character objects. Like that discussedearlier, the arrow directions of these respective arrow objects are madeto be indicators for informing the user of a flick direction whenperforming a flick gesture from the finger contact point 10 position(the center of the keypad layout).

Herein, in the example in FIG. 36, numerals and symbols are assigned torespective numeral objects, but obviously these assignments are anexample, and the assignments may be changed as discussed earlier, andother characters and symbols, other symbols, etc. may also be assignedas function information. Also, the numeral object group 24 may also notbe displayed in cases such as when the user has mostly memorized theassignments of numerals, etc. to each numeral object. Furthermore, thedisplay and non-display of the numeral object group 24 may also beappropriately switched according to an arbitrary setting by the user,for example.

If for example the user performs a flick gesture toward the disposeddirection of a desired numeral while in a state wherein respectivenumerals, etc. are assigned to respective numeral objects in the numeralobject group 24 as illustrated in the above FIG. 36, a mobileinformation device of the present embodiment determines that thenumeral, etc. in the direction of that flick gesture has been selectedby the user. Then, when a user-desired numeral is selected, a mobileinformation device of the present embodiment inputs the selectednumeral, etc. into the text box 2, etc.

A detailed process flow for realizing numeral input as discussed abovein a mobile information device of the present embodiment will be givenlater.

(Exemplary Menu Operation)

In an information input technique of the present embodiment, selectionoperations for tiered menu items, for example, are made to be realizableby for example one tap gesture and two flick gestures, excluding someexceptions. In the examples hereinafter, an example is given wherein themenu tiers have two tiers, but menu tiers in the present embodiment mayalso be made to have three tiers or a greater number of tiers.

FIGS. 37 to 45 illustrate exemplary gesture operations on a touch paneland exemplary screen transitions when selecting menu items, taking menuitems during a music playback mode as an example of menu selectionoperations in the case where the menu tiers consist of two tiers.Herein, in the description hereinafter, respective exemplary menu itemslike those illustrated in FIGS. 39 and 40 and in FIGS. 43 and 44 aregiven as an example of tiered menu items during a music playback mode,but the present embodiment is obviously not limited to this example.Also, in the example hereinafter, menu items and exemplary selectionoperations therefor during a music playback mode are given, but thepresent embodiment is not limited to this example, and it is needless tosay that the present embodiment is applicable to various menu items andselection operations therefor which are usable on a mobile informationdevice.

FIG. 37 illustrates an example wherein a mobile information device ofthe present embodiment has entered a music playback mode, and whereinthe currently playing song title and playback time are displayed on adisplay screen 1.

If for example a desired position on a touch panel is tapped by the useras illustrated in FIG. 38 in the case where a mobile information devicehas entered a music playback mode, a mobile information device of thepresent embodiment displays various playback control items during themusic playback on the display screen as respective menu items, whilealso transitioning to a full screen takeover mode such that these menuitems enter a state of being selectable by the user's gestureoperations. Then, in the case of a full screen takeover mode during themusic playback, a mobile information device of the present embodimentdisplays a takeover mode screen 1Jb like that illustrated in FIG. 39.Herein, in the case of this example, music playback is executed in thebackground. Also, in the examples in FIG. 38 and FIG. 39, the fingercontact point 10 is similar to that discussed earlier.

As an example herein, a group object group 40 like that illustrated inFIG. 39 is disposed on the takeover mode screen 1Jb in the case of thepresent embodiment.

The group object group 40 exemplified in FIG. 39 is made to be a groupof group objects respectively representing groups in which respectivemenu items for various user-operable playback controls during musicplayback are tiered (hereinafter designated menu groups), the groupobjects being disposed for example on the circumference of concentriccircles centered on a finger contact point 10. Obviously, the groupobject group 40 illustrated in FIG. 39 is merely an example, andrespective group objects may also be disposed at positions based on akeypad layout as discussed earlier, for example. Also, in the case ofthe group object group 40 in FIG. 39, arrow objects, etc. pointing fromthe finger contact point 10 to the respective group objects are notdrawn, but arrow objects may also be drawn as indicators for flickgestures, similarly to that discussed earlier.

In the case of the example in FIG. 39, the respective group objectsconstituting the group object group 40 include, as an example, a groupobject corresponding to a menu group for volume control, a group objectcorresponding to a menu group for skip control, a group objectcorresponding to a menu group for fast forward control, and a groupobject corresponding to a menu group for stop/play control. In otherwords, these menu groups are made to be groups of music playback controlfunctions collected per category.

Assigned to the volume control menu group is for example a two-tier menuitem with a menu item representing operations corresponding to volumecontrol, and underneath it menu items for arbitrarily raising/loweringthe volume during music playback. Assigned to the skip control menugroup is for example a two-tier menu item with a menu item representingoperations corresponding to skip control, and underneath it menu items,etc. for selecting play first, play from beginning, skip, random, etc.,for example. Assigned to the fast forward control menu group is forexample a two-tier menu item with a menu item representing operationscorresponding to fast forward control, and underneath it menu items,etc. for selecting frame step back, rewind, fast forward, frame stepforward, etc., for example. Assigned to the stop/play control menu groupis for example a two-tier menu item with a menu item representingoperations corresponding to stop/play control, and underneath it menuitems, etc. for selecting stop and play, pause, off, etc., for example.In other words, these menu items are made to correspond to respectiveadjustment items in the category of the previously selected controlfunction.

Furthermore, in this example in FIG. 39, the volume control menu groupis disposed on the circumference of concentric circles centered on thefinger contact point 10 in the downward direction of the finger contactpoint 10. Similarly, the skip control menu group is disposed on thecircumference of the concentric circles in the left horizontal directionof the finger contact point 10. The stop/play control menu group isdisposed on the circumference of the concentric circles in the upwarddirection of the finger contact point 10. The fast forward control menugroup is disposed on the circumference of the concentric circles in theright horizontal direction of the finger contact point 10.

Herein, in this example, and similarly to that discussed earlier, it isalso possible to provide a group object not assigned with a menu groupin advance, and appropriately assign a user-desired menu group to thatgroup object as function information, for example. Also, it isconfigured such that even group objects already assigned with a menugroup can have their respective menu group assignments appropriatelychanged to other menu groups or other functions.

Also, in this example, and similarly to that discussed earlier, it isillustrated how a group object group 40 is displayed on a takeover modescreen 1Jb, but the group object group 40 may also not be displayed incases such as when the user has memorized the positional relationshipsof the respective group objects and the assignments between each groupobject and menu group, for example. Also, in the present embodiment, thedisplay and non-display of the group object group 40 may also beappropriately switched according to an arbitrary setting by the user,for example.

Next, if a flick gesture is conducted toward the disposed direction of auser-desired menu group while in a state wherein respective menu groupsare assigned on the circumference of concentric circles centered on thefinger contact point 10 as illustrated in FIG. 30 discussed above, amobile information device of the present embodiment determines that themenu group in the direction of that flick gesture has been selected bythe user. Herein, in the case where volume adjustment is performed, forexample, the flick gesture direction at this time becomes the downwarddirection from the finger contact point 10 as illustrated in FIG. 40,and thus the menu group corresponding to the volume control item isselected. Herein, in this example in FIG. 40, the finger contact points10 a and 10 b in the drawing are similar to that discussed earlier.

If a user-desired menu group is selected as in the above FIG. 40, amobile information device of the present embodiment goes back to atakeover mode screen 1Jb like that illustrated in FIG. 41, and in astate wherein the menu group selected by the user is remembered.

Also, in the case where a user-desired menu group is selected from thegroup object group 40, a mobile information device of the presentembodiment is also made to be capable of displaying a given objectrelated to the selected menu group on a takeover mode screen 1Jb.Herein, in the case where the volume control menu group from the groupobject group as in the example discussed above, a mobile informationdevice is made to be capable of displaying for example a bar object 50representing the volume as the given object related to volume control,as illustrated in FIG. 41.

Next, if for example the user's finger, etc. contacts a desired positionon the touch panel as illustrated in FIG. 42 in the case where thevolume control menu group has been selected, a mobile information deviceof the present embodiment causes a volume adjustment-related menu objectgroup 41 like that illustrated in FIG. 43 to be displayed on thetakeover mode screen 1Jb. Herein, in these examples in FIG. 42 and FIG.43, the finger contact point 10 is similar to that discussed earlier.

In the present embodiment, the menu object group 41 illustrated in FIG.43 is made to be a group of objects corresponding to respective menusbelonging to the previously selected menu group for volume control, theobjects being disposed on the circumference of concentric circlescentered on a finger contact point 10 similarly to that discussedearlier. Herein, the menu object group 41 illustrated in FIG. 43 ismerely an example, and respective menu objects may also be disposed atpositions based on the above-discussed keyboard layout, for example.Also, in the case of the menu object group 41 in FIG. 43, arrow objects,etc. pointing from the finger contact point 10 to the respective menuobjects are not drawn, but arrow objects may also be drawn as indicatorsfor flick gestures, similarly to that discussed earlier.

In the case of the example in FIG. 43, the respective menu objectsconstituting the menu object group 41 include, as an example, a menuobject corresponding to a “Low” volume menu item, a menu objectcorresponding to a “High” volume menu item, a menu object correspondingto a “Mute” volume menu item, and a menu object corresponding to an“Auto” volume menu item.

In other words, in this example in FIG. 43, a menu item for raising thevolume is assigned to the “High” volume menu object, and a menu item forlowering the volume is assigned to the “Low” volume menu object. A menuitem for turning on/off a volume mute function is assigned to the “Mute”volume menu object. A menu item for turning on/off a function thatautomatically adjusts the volume according to for example the externalvolume is assigned to the “Auto” volume menu object.

Then, if for example the user performs a flick gesture toward thedisposed direction of a desired menu item while in a state whereinrespective menu items are assigned on the circumference of concentriccircles centered on a finger contact point 10 as in the above menuobject group 41, a mobile information device of the present embodimentdetermines that the menu item in the direction of that flick directionhas been selected by the user. For example, in the case where a flickgesture is made in the disposed direction of a menu object assigned withthe “Low” volume menu item as illustrated in FIG. 44, a mobileinformation device of the present embodiment adjusts the volume in thedirection of lower volume. Herein, the finger contact points 10 a and 10b and the arrow linking them in FIG. 44 are similar to that discussedearlier.

After that, a mobile information device of the present embodiment causesthe bar object 50 representing the volume to change to a displayrepresenting the volume level after the volume was lowered, while alsogoing back to a takeover mode screen 1Jb.

Meanwhile, in the case where for example the “High” volume menu objectis selected from the menu object group 41, a mobile information deviceof the present embodiment adjusts the volume in the direction of highervolume, while also causing the bar object 50 to change to a displayrepresenting the volume level after the volume was raised. As anotherexample, in the case where the “Mute” volume menu object is selectedfrom the menu object group 41, a mobile information device of thepresent embodiment adjusts the “Mute” volume on if for example the“Mute” volume was in an off state in its previous state, and incontrast, adjusts the “Mute” volume off if for example the “Mute” volumewas in an on state in its previous state. As another example, in thecase where the “Auto” volume menu object is selected from the menuobject group 41, a mobile information device of the present embodimentadjusts the “Auto” volume on if for example the “Auto” volume was in anoff state in its previous state, and in contrast, adjusts the “Auto”volume off if for example the “Auto” volume was in an on state in itsprevious state.

Besides the above, in the case where for example a fast forward controlmenu group is selected by the user from the group object group 40illustrated in FIG. 39 discussed above, a menu object corresponding to adouble speed fast forward menu item, a menu object corresponding to atriple speed fast forward menu item, respective menu objectscorresponding to respective fast forward menu items even faster than theabove, a menu object corresponding to a single speed rewind menu item, amenu object corresponding to a double speed rewind menu item, a menuobject corresponding to respective rewind menu items even faster thanthe above, a menu object corresponding to a menu item for returning tosingle speed playback, etc. are for example disposed similarly to thatdiscussed earlier as one example of a menu object group 41. Then, whenthe user selects a desired menu item from among the above with a flickgesture, a mobile information device of the present embodiment executesplayback speed control according to the selected menu item. Herein, inthe case where a playback speed adjustment is made in this way, givenaudio, etc. representing the playback speed may also be displayed on atakeover mode screen 1Jb.

Also, in the case where for example a skip control menu group isselected by the user from the group object group 40 illustrated in FIG.39 discussed above, respective menu objects for play first, play frombeginning, skip, random, etc. are for example disposed similarly to thatdiscussed earlier as one example of a menu object group 41. Then, whenthe user selects a desired menu item from among the above with a flickgesture, a mobile information device of the present embodiment executesplayback according to the selected menu item. Herein, in the case wherea skip adjustment is made in this way, given audio, etc. representingthe skip state may also be displayed on a takeover mode screen 1Jb.

Also, in the case where for example a stop/play control menu group isselected by the user from the group object group 40 illustrated in FIG.39 discussed above, a menu object corresponding to a stop playback menuitem, a menu object corresponding to a start playback menu item, a menuobject corresponding to a pause menu item, a menu object correspondingto a cancel pause (off) menu item, etc. are for example disposedsimilarly to that discussed earlier as one example of a menu objectgroup 41. Then, when the user selects a desired menu item from among theabove with a flick gesture, a mobile information device of the presentembodiment executes playback control according to the selected menuitem. Herein, in the case where stop/play control is made in this way,given audio, etc. representing the stop/play control state may also bedisplayed on a takeover mode screen 1Jb.

A more detailed process flow, etc. for realizing menu operations likethose discussed above will be given later.

(Exemplary Information Search Using a Phone Book)

In an information input technique of the present embodiment, informationinput operations for searching information stored inside a desiredinformation storage unit such as for example an address book, phonebook, etc. is realizable by for example at least one tap gesture and oneflick gesture, excluding some exceptions.

Herein, in the description hereinafter, an example is given wherein thedesired information storage unit is made to be a phone book inside amobile information device, and wherein registered information (records)from that phone book is searched. Also, in the example hereinafter, anexample is given wherein a name from the phone book is searched for,with the characters “KUSANO” taken as the search keyword as an example.Obviously, it is needless to say that information searching in thepresent embodiment is also applicable to the searching of informationstored in various other information storage units.

FIGS. 46 to 55 illustrate exemplary gesture operations and exemplaryscreen transitions when searching for the registered information“KUSANO” from a phone book as an example. Herein, in the presentembodiment, the operational mode of a mobile information device at thistime is made to be an information search mode, and a phone book is madeto be the search target in this information search mode.

FIG. 46 illustrates an exemplary display screen in the case where amobile information device of the present embodiment has entered aninformation search mode and where the search target is set to a phonebook.

If for example a desired position on the touch panel is tapped by theuser as illustrated in FIG. 47 in the case where a mobile informationdevice has entered an information search mode that searches forregistered information from a phone book, a mobile information device ofthe present embodiment transitions to a full screen takeover modesimilar to the exemplary operation during character input in theJapanese character input mode discussed earlier. Herein, the takeovermode screen 1Jc in the case of this example is not provided with thefunction areas 12 to 15 discussed earlier, but obviously those functionareas 12 to 15 may also be disposed.

If the user's finger, etc. contacts a desired position on the touchpanel as illustrated in FIG. 47 after transitioning to a full screentakeover mode in the information search mode, a mobile informationdevice causes a group object group 22 similar to that during Japaneseinput discussed earlier to be displayed on the takeover mode screen 1Jc,as illustrated in FIG. 48. Herein, the finger contact point 10 in FIG.47 and FIG. 48 is similar to that discussed earlier. Also, similarly tothat discussed earlier, the group object group 22 may also not bedisplayed in cases such as when the user has mostly memorized thepositional relationships of the respective group objects, etc.Furthermore, in this example, and similarly to that discussed earlier,the display and non-display of the group object group 22 may also beappropriately switched according to an arbitrary setting by the user.

Next, if the user performs a flick gesture toward the disposed directionof also desired character group similarly to that discussed earlierwhile the group object group 22 is being displayed, a mobile informationdevice of the present embodiment determines that the character group inthe direction of that flick gesture has been selected by the user.

Herein, in the case of searching desired information from a desiredinformation storage unit using for example a Japanese search keyword asin the present embodiment, the first flick gesture direction is made tobe the direction selecting the character group of the consonant includedin for example the first character of the character string constitutingthe search keyword. In other words, in the case where for example aregistered name is searched from a phone book with “KUSANO” as thesearch keyword, the first flick gesture direction is first made to bethe direction selecting the character group of the consonant “k”included in the first character “ku” of the hiragana reading “kusano” ofthe above “KUSANO”. For this reason, the first flick gesture directionwhen inputting the above characters “KUSANO” is made to be the directionin which is disposed the character group of the consonant “k” includedin the first character “ku” of the hiragana reading “kusano” of theabove “KUSANO”, or in other words the upward direction from the fingercontact point 10, as illustrated by the example in FIG. 49.

If the character group of the consonant “k” is selected by a first flickgesture as described above, a mobile information device of the presentembodiment extracts from a phone book a group of respectively registerednames for which the consonant of the first character in the hiraganareading of the name registered in the phone book is the consonant “k”,as illustrated in FIG. 50. Then, a mobile information device of thepresent embodiment displays on a takeover mode screen 1Jc a searchinformation list (record list) 60 consisting of the registered namegroup extracted from the phone book. Herein, in the case where there isone registered name in the search information list 60 at this time, andwhen that registered name is the above “KUSANO”, a phone book searchtaking “KUSANO” as the search keyword is terminated. A mobileinformation device of the present embodiment may also displayinformation registered in a phone book in association with the name“KUSANO” (phone number, address, and other information, for example) ona display screen when the touch panel is for example tappedcorresponding to where the above “KUSANO” is being displayed when aphone book search has finished is tapped.

Next, if for example the user's finger, etc. additionally contacts adesired position on the touch panel as illustrated in FIG. 51 in thecase where the search information list 60 comprises a plurality ofnames, etc., a mobile information device of the present embodimentcauses a group object group 22 similar to FIG. 48 discussed earlier tobe displayed on the takeover mode screen 1Jc, as illustrated in FIG. 52.

Then, if the user performs a flick gesture in the disposed direction ofalso desired character group similar to that discussed earlier while ina state wherein the search information list 60 and a group object group22 is being displayed, a mobile information device of the presentembodiment determines that the character group in the direction of thatflick gesture has been selected by the user.

In this way, in the case where a flick gesture is additionally performedwith respect to a group object group 22 while in a state wherein asearch information list 60 has been obtained by a first informationsearch, a mobile information device of the present embodiment executesprocessing to further refine the information from the search informationlist. In the present embodiment, a search that further refinesinformation from a search information list obtained by a firstinformation search is conducted by for example selecting the charactergroup of the consonant included in the second character of the characterstring constituting the search keyword. In other words, in the casewhere for example the above “KUSANO” is made to be the search keyword,the second flick gesture direction is made to be the direction selectingthe character group of the consonant “s” included in the secondcharacter “sa” of the hiragana reading “kusano” of “KUSANO”. For thisreason, the second flick gesture direction is made to be the directionin which is disposed the character group of the consonant “s” includedin the second character “sa” of the hiragana reading “kusano” of theabove “KUSANO”, or in other words the direction approximately 45 degreesupward and to the right from the finger contact point 10, as illustratedby the example in FIG. 53.

If the character group of the consonant “s” is selected by a secondflick gesture as described above, a mobile information device of thepresent embodiment refines the search information list obtained by thefirst information search to a group of respectively registered names forwhich the consonant of the first character and the consonant of thesecond character in the hiragana reading of the name registered in thephone book are the consonant “k” and the consonant “s”, respectively.Then, a mobile information device of the present embodiment displays ona takeover mode screen 1Jc a search information list 61 consisting of aname group refined from the search information list given by the firstinformation search, or in other words a search information list given bythe second information search, as illustrated in FIG. 54. In otherwords, during the information search, “consonant” selection in Japaneseinput is repeated, and refined searches are conducted so as to searchfor information that matches the sequence of these several selected“consonants”.

Herein, since a plurality of names are still included in the informationsearch list in the example in FIG. 54, refined searches are additionallyconducted similarly to that discussed above. In other words, similarlyto that discussed above, a tap gesture is performed, and the charactergroup of the consonant “n” included in the third character “no” of thehiragana reading “kusano” of “KUSANO” is selected by a third flickgesture. In this way, if refined searches are additionally conducted onthe search information list given by the second information search, amobile information device of the present embodiment displays on atakeover mode screen 1Jc a search information list 62 where theregistered name has become “KUSANO”, as illustrated in FIG. 55. In sodoing, a phone book search with the above “KUSANO” as the search keywordis ended. Then, similarly to that discussed above, a mobile informationdevice of the present embodiment may also display information registeredin a phone book in association with the name “KUSANO” (phone number,address, and other information) on a display screen in the case wherethe touch panel is for example tapped corresponding to where the above“KUSANO” is being displayed when a phone book search has finished.

A detailed process flow for realizing an information search like thatdiscussed above in a mobile information device of the present embodimentwill be given later.

(Information Input by Consecutive Flick Gestures)

Besides the examples of selecting desired characters and information byselection using several flick gestures as discussed above, a mobileinformation device of the present embodiment is also configured toenable similar selection of desired characters and information even inthe case where for example several consecutive flick gestures areperformed in a state wherein a finger, etc. is not released from a touchpanel.

FIG. 56 illustrates an example of flick gestures performed in a statewherein a finger is not released from a touch panel. Herein, the fingercontact points 10 a, 10 b, and 10 c in FIG. 56 are points for easilyvisualizing in the drawing the positions contacted by the user's finger,etc. on a display screen (on a touch panel), similarly to that discussedearlier.

This FIG. 56 illustrates an example wherein the user's finger, etc. at adesired position on a touch panel slides in the arrow directionextending from a finger contact point 10 a to a finger contact point 10b while the user's finger is in a state of contact with the touch panel,and additionally, wherein the user's finger, etc. slides in the arrowdirection extending from the finger contact point 10 b to a fingercontact point 10 c while the user's finger is in a state of contact withthe touch panel.

In other words, according to this example in FIG. 56, the arrowdirection extending from the finger contact point 10 a to the fingercontact point 10 b is input by the user, and subsequently, the arrowdirection extending from the finger contact point 10 b to the fingercontact point 10 c is input by the user. A mobile information device ofthe present embodiment in this case conducts for example group selectionas discussed earlier according to the user input of the arrow directionextending from the finger contact point 10 a to the finger contact point10 b, and conducts selection of information belonging to the previouslyselected group according to the subsequent user input of the arrowdirection extending from the finger contact point 10 b to the fingercontact point 10 c.

According to consecutive input like that illustrated in this FIG. 56,since group selection followed by information selection within the groupbecomes possible without releasing a finger from the touch panel, fasterinformation input becomes possible. Herein, in this example in FIG. 56,object groups corresponding to a group and information within a groupsimilar to that discussed earlier may also be displayed for example atthe finger contact point 10 b, in the vicinity of the finger contactpoint 10, etc.

Meanwhile, it is also possible to inform the user that a user operationhas been received, etc. in an easily understandable way by conductingvibrator rumbling and changing the vibrator rumble pattern and typeaccording to the particular stage of information input, etc. as feedbackwith respect to gesture operations from the user during variousinformation input like that discussed above.

(Exemplary Correspondence Tables Between Character, Menu, RegisteredInformation, Etc. And Flick Gesture Directions)

In order to realize processing for English character input, Japanesecharacter input, numeral input, menu selection, information search, etc.as discussed above, a mobile information device of the presentembodiment stores correspondence tables for respective character inputmodes like those described hereinafter in for example the memory unit105 discussed earlier. Herein, the respective correspondence tables maybe extracted into the memory unit 105 by activation of an informationinput control program of the present embodiment, or readied in thememory unit 105 in advance.

FIG. 57 illustrates an input event—input ID correspondence table for amobile information device of the present embodiment to recognize theabove tap gestures with respect to a touch panel and respective flickdirections for the above flick gestures during the respective characterinput modes discussed earlier. Meanwhile, FIG. 58 illustrates a diagramfor visualizing directions corresponding to the input IDs in FIG. 57.

In the correspondence table in FIG. 57, the input events correspond tothe tap gestures and the respective flick directions for the flickgestures. The input IDs are IDs individually assigned to each inputevent.

In other words, in the case where a gesture operation from the user isperformed on the touch panel after transitioning to the full screentakeover mode, a mobile information device of the present embodimentdetermines which input event the gesture operation from the user was onthe basis of the correspondence table illustrated in FIG. 57, and alsorecognizes the input ID corresponding to that input event.

Described specifically, in the case where a tap gesture is performed asan input event after transitioning to a full screen takeover mode, amobile information device of the present embodiment references the inputID “5” corresponding to that input event from the correspondence tablein FIG. 57. As illustrated in FIG. 58, the input ID “5” becomes theposition of the finger contact point 10. As another example, in the casewhere a flick gesture is performed from the finger contact point 10contacted by the user's finger on the touch panel toward the upper-leftdirection illustrated by the arrow A1 in FIG. 58 (in other wordsapproximately 45 degrees upward and to the left), a mobile informationdevice references the input ID “1” corresponding to the input event fromthe correspondence table in FIG. 57. As another example, in the casewhere a flick gesture is performed from the finger contact point 10toward the upward direction illustrated by the arrow A2 in FIG. 58, amobile information device references the input ID “2” corresponding tothat input event from the correspondence table. Also, in the case wherea flick gesture is performed from the finger contact point 10 toward theupper-right direction illustrated by the arrow A3 in FIG. 58 (in otherwords approximately 45 degrees upward and to the right), a mobileinformation device references the input ID “3” corresponding to thatinput event from the correspondence table. Similarly, a mobileinformation device of the present embodiment respectively references theinput ID “4” at the time of an input event for a flick gesture in theleft direction illustrated by the arrow A4 in FIG. 58 (left horizontaldirection), the input ID “6” at the time of an input event for a flickgesture in the right direction illustrated by the arrow A6 in FIG. 58(right horizontal direction), the input ID “7” at the time of an inputevent for a flick gesture in the lower-left direction illustrated by thearrow A7 in FIG. 58 (approximately 45 degrees downward and to the left),the input ID “8” at the time of an input event for a flick gesture inthe downward direction illustrated by the arrow A8 in FIG. 58, and theinput ID “9” at the time of an input event for a flick gesture in thelower-right direction illustrate by the arrow A9 in FIG. 58(approximately 45 degrees downward and to the right). Also, a mobileinformation device respectively references the input ID “0” at the timeof an input event for a fast flick gesture in the downward directionillustrated by the arrow A0 in FIG. 58, the input ID “11” at the time ofan input event for a fast flick gesture in the left directionillustrated by the arrow A11 in FIG. 58 (left horizontal direction), andthe input ID “12” at the time of an input event for a fast flick gesturein the right direction illustrated by the arrow A12 in FIG. 58 (righthorizontal direction), for example. In this way, a mobile informationdevice of the present embodiment references input IDs corresponding torespective input events from the correspondence table illustrated inFIG. 57.

Then, by referencing respective input ID correspondence tables likethose illustrated in FIGS. 59 to 70 on the basis of input IDscorresponding to the input events, a mobile information device of thepresent embodiment selects character, numeral, or menu item groupscorresponding to the input IDs, and additionally selects characters,menu items, etc. within the selected groups.

FIG. 59 illustrates a correspondence table between the input IDs andrespective groups in an English character input mode.

In this correspondence table in FIG. 59, the group ID is an IDindividually assigned to each group during an English character inputmode (group ID). In the case of an English character input mode, thegroup ID “1” is associated with the input ID “1”, the group ID “2” withthe input ID “2”, the group ID “3” with the input ID “3”, the group ID“4” with the input ID “4”, the group ID “5” with the input ID “5”, thegroup ID “6” with the input ID “6”, the group ID “7” with the input ID“7”, the group ID “8” with the input ID “8”, and the group ID “9” withthe input ID “9”, respectively. Meanwhile, group IDs are not assigned tothe input ID “0”, the input ID “11”, and the input ID “12”, and theseinput IDs are configured such that various applied uses, such as thefunction information, etc. discussed earlier, are applicable thereto.

FIG. 60 illustrates a correspondence table between the input IDs and IDscorresponding to English characters, etc. included in an respectivegroup IDs referenced from the correspondence table in FIG. 59 (internalgroup IDs) during an English character input mode.

In the correspondence table illustrated in FIG. 60, internal group IDs“No. 1”, “No. 2”, “No. 3”, “No. 4”, “No. 5”, “No. 6”, “No. 7”, “No. 8”,and “No. 9” correspond to the respective internal group IDs in thecorrespondence tables in FIGS. 61 to 63. Furthermore, in the case of anEnglish character input mode, the internal group ID “No. 1” isassociated with the input ID “1”, the internal group ID “No. 2” with theinput ID “2”, the internal group ID “No. 3” with the input ID “3”, theinternal group ID “No. 4” with the input ID “4”, the internal group ID“No. 5” with the input ID “5”, the internal group ID “No. 6” with theinput ID “6”, the internal group ID “No. 7” with the input ID “7”, theinternal group ID “No. 8” with the input ID “8”, and the internal groupID “No. 9” with the input ID “9”, respectively. Meanwhile, internalgroup IDs are not assigned to the input ID “0”, the input ID “11”, andthe input ID “12”, and these input IDs are configured such that variousapplied uses, such as the function information, etc. discussed earlier,are applicable thereto.

Herein, in the present embodiment, in the case where an Englishcharacter input mode is the English character keypad-relative input modediscussed earlier, the internal group ID IDs illustrated in the aboveFIG. 60 are respectively associated with respective English charactersfor the English character keypad-relative input mode as illustrated bythe correspondence table in FIG. 61.

In other words, the correspondence table illustrated in FIG. 61illustrates a correspondence table of correspondences between the groupIDs in FIG. 59 and the respective internal group IDs in FIG. 60, as wellas respective English characters belonging to groups with respectivegroup IDs.

Described specifically, in the case of the English characterkeypad-relative input mode discussed earlier, the group with the groupID “1” is for example a group corresponding to respective symbols suchas “.”, “_”, “@”, and “-”, wherein the symbol “.” is associated with theinternal group ID “No. 2”, the symbol “_” with the internal group ID“No. 4”, the symbol “@” with the internal group ID “No. 6”, and thesymbol “-” with the internal group ID “NO. 8” of the group ID “1”,respectively, as illustrated by the correspondence table in FIG. 61.Also, the group with the group ID “2” is a group corresponding to therespective English characters “a, b, c”, wherein the English character“a” is associated with the internal group ID “No. 2”, the Englishcharacter “b” with the internal group ID “No. 6”, and the Englishcharacter “c” with the internal group ID “No. 8” of the group ID “2”,respectively. Similarly, the group with the group ID “3” is a groupcorresponding to the respective English characters “d, e, f”, whereinthe English character “d” is associated with the internal group ID “No.2”, the English character “e” with the internal group ID “No. 6”, andthe English character “f” with the internal group ID “No. 8” of thegroup ID “3”, respectively. The group with the group ID “4” is a groupcorresponding to the respective English characters “g, h, i”, whereinthe English character “g” is associated with the internal group ID “No.2”, the English character “h” with the internal group ID “No. 6”, andthe English character “i” with the internal group ID “No. 8” of thegroup ID “4”, respectively. The group with the group ID “5” is a groupcorresponding to the respective English characters “j, k, 1”, whereinthe English character “j” is associated with the internal group ID “No.2”, the English character “k” with the internal group ID “No. 6”, andthe English character “1” with the internal group ID “No. 8” of thegroup ID “5”, respectively. The group with the group ID “6” is a groupcorresponding to the respective English characters “m, n, o”, whereinthe English character “m” is associated with the internal group ID “No.2”, the English character “n” with the internal group ID “No. 6”, andthe English character “o” with the internal group ID “No. 8” of thegroup ID “6”. Also, the group with the group ID “7” is a groupcorresponding to the respective English characters “p, q, r, s”, whereinthe English character “p” is associated with the internal group ID “No.2”, the English character “s” with the internal group ID “No. 4”, theEnglish character “q” with the internal group ID “No. 6”, and theEnglish character “r” with the internal group ID “No. 8” of the group ID“7”. The group with the group ID “8” is a group corresponding to therespective English characters “t, u, v”, wherein the English character“t” is associated with the internal group ID “No. 2”, the Englishcharacter “u” with the internal group ID “No. 6”, and the Englishcharacter “v” with the internal group ID “No. 8” of the group ID “8”.The group with the group ID “9” is a group corresponding to therespective English characters “w, x, y, z”, wherein the Englishcharacter “w” is associated with the internal group ID “No. 2”, theEnglish character “z” with the internal group ID “No. 4”, the Englishcharacter “x” with the internal group ID “No. 6”, and the Englishcharacter “y” with the internal group ID “No. 8” of the group ID “9”.

Also, in the present embodiment, in the case where an English characterinput mode is the English character 4 group-relative input modediscussed earlier, the internal group ID IDs illustrated in the aboveFIG. 60 are respectively associated with respective English charactersfor the English character 4 group-relative input mode as illustrated bythe correspondence table in FIG. 62.

In other words, the correspondence table illustrated in FIG. 62illustrates a correspondence table of correspondences between the groupIDs in FIG. 59 and the respective internal group IDs in FIG. 60, as wellas respective English characters belonging to groups with respectivegroup IDs in the case where an English character input mode is theEnglish character 4 group-relative input mode discussed earlier. Herein,in the case of an English character 4 group-relative input mode,internal group IDs are associated with the group ID “2”, the group ID“4”, the group ID “6”, and the group ID “8”.

Described specifically, in the case of the English character 4group-relative input mode discussed earlier, the group with the group ID“2” is a group corresponding to the respective English characters “a, b,c, d, e, f, g”, wherein the English character “e” is associated with theinternal group ID “No. 1”, the English character “a” with the internalgroup ID “No. 3”, the English character “f” with the internal group ID“No. 4”, the English character “b” with the internal group ID “No. 6”,the English character “g” with the internal group ID “No. 7”, theEnglish character “d” with the internal group ID “No. 8”, and theEnglish character “c” with the internal group ID “No. 9” of the group ID“2”, respectively, as illustrated by the correspondence table in FIG.62. Similarly, the group with the group ID “4” is a group correspondingto the respective English characters “v, w, x, y, z”, wherein theEnglish character “x” is associated with the internal group ID “No. 1”,the English character “v” with the internal group ID “No. 3”, theEnglish character “y” with the internal group ID “No. 4”, the Englishcharacter “z” with the internal group ID “No. 6”, and the Englishcharacter “w” with the internal group ID “No. 9” of the group ID “4”,respectively. The group with the group ID “6” is a group correspondingto the respective English characters “h, i, j, k, l, m, n”, wherein theEnglish character “1” is associated with the internal group ID “No. 1”,the English character “h” with the internal group ID “No. 3”, theEnglish character “m” with the internal group ID “No. 4”, the Englishcharacter “i” with the internal group ID “No. 6”, the English character“n” with the internal group ID “No. 7”, the English character “k” withthe internal group ID “No. 8”, and the English character “j” with theinternal group ID “No. 9” of the group ID “6”, respectively. The groupwith the group ID “8” is a group corresponding to the respective Englishcharacters “o, p, q, r, s, t, u”, wherein the English character “s” isassociated with the internal group ID “No. 1”, the English character “o”with the internal group ID “No. 3”, the English character “t” with theinternal group ID “No. 4”, the English character “p” with the internalgroup ID “No. 6”, the English character “u” with the internal group ID“No. 7”, the English character “r” with the internal group ID “No. 8”,and the English character “q” with the internal group ID “No. 9” of thegroup ID “8”, respectively.

Also, in the present embodiment, in the case where an English characterinput mode is the English word-relative input mode discussed earlier,the internal group ID IDs illustrated in the above FIG. 60 arerespectively associated with respective English characters for theEnglish word-relative input mode as illustrated by the correspondencetable in FIG. 63.

In other words, the correspondence table illustrated in FIG. 63illustrates a correspondence table of correspondences between the groupIDs in FIG. 59 and the respective internal group IDs in FIG. 60, as wellas respective English characters belonging to groups with respectivegroup IDs in the case where an English character input mode is theEnglish word-relative input mode discussed earlier. Herein, in the caseof an English word-relative input mode, internal group IDs are notassociated with the group ID “5”, for example.

Described specifically, in the case of the English word-relative inputmode discussed earlier, the group with the group ID “1” is a groupcorresponding to the English word “bang”, wherein the English character“b” is associated with the internal group ID “No. 2”, the Englishcharacter “g” with the internal group ID “No. 4”, the English character“a” with the internal group ID “No. 6”, and the English character “n”with the internal group ID “No. 8” of the group ID “1”, respectively, asillustrated by the correspondence table in FIG. 63. Similarly, the groupwith the group ID “2” is a group corresponding to the English word“chip”, wherein the English character “c” is associated with theinternal group ID “No. 2”, the English character “p” with the internalgroup ID “No. 4”, the English character “h” with the internal group ID“No. 6”, and the English character “i” with the internal group ID “No.8” of the group ID “2”. The group with the group ID “3” is a groupcorresponding to the English word “desk”, wherein the English character“d” is associated with the internal group ID “No. 2”, the Englishcharacter “k” with the internal group ID “No. 4”, the English character“e” with the internal group ID “No. 6”, and the English character “s”with the internal group ID “No. 8” of the group ID “3”. The group withthe group ID “4” is a group corresponding to the English word “from”,wherein the English character “f” is associated with the internal groupID “No. 2”, the English character “m” with the internal group ID “No.4”, the English character “r” with the internal group ID “No. 6”, andthe English character “o” with the internal group ID “No. 8” of thegroup ID “4”. The group with the group ID “6” is a group correspondingto the English word “july”, wherein the English character “j” isassociated with the internal group ID “No. 2”, the English character “y”with the internal group ID “No. 4”, the English character “u” with theinternal group ID “No. 6”, and the English character “1” with theinternal group ID “No. 8” of the group ID “6”. The group with the groupID “7” is a group corresponding to the English word “wave”, wherein theEnglish character “w” is associated with the internal group ID “No. 2”,the English character “e” with the internal group ID “No. 4”, theEnglish character “a” with the internal group ID “No. 6”, and theEnglish character “v” with the internal group ID “No. 8” of the group ID“7”. The group with the group ID “8” is a group corresponding to theEnglish word “taxy”, wherein the English character “t” is associatedwith the internal group ID “No. 2”, the English character “y” with theinternal group ID “No. 4”, the English character “a” with the internalgroup ID “No. 6”, and the English character “x” with the internal groupID “No. 8” of the group ID “8”. The group with the group ID “9” is agroup corresponding to the English word “quiz”, wherein the Englishcharacter “q” is associated with the internal group ID “No. 2”, theEnglish character “z” with the internal group ID “No. 4”, the Englishcharacter “u” with the internal group ID “No. 6”, and the Englishcharacter “i” with the internal group ID “No. 8” of the group ID “9”.

FIG. 64 illustrates a correspondence table between the input IDs andrespective consonants in a Japanese character input mode.

In this correspondence table in FIG. 64, “a, k, s, t, n, h, m, y, r, w”are assigned to respective consonants as consonant IDs. Additionally, inthe case of the Japanese character input mode, the consonant ID “w” isassigned to the input ID “0”, and similarly, the consonant ID “a” to theinput ID “1”, the consonant ID “s” to the input ID “3”, the consonant ID“t” to the input ID “4”, the consonant ID “n” to the input ID “5”, theconsonant ID “h” to the input ID “6”, the consonant ID “m” to the inputID “7”, the consonant ID “y” to the input ID “8”, and the consonant ID“r” to the input ID “9”, respectively. Also, a small characterconversion function applied use is assigned as a consonant ID to theinput ID “11”, and a dakuten conversion function applied use is assignedas a consonant ID to the input ID “12”.

FIG. 65 illustrates a correspondence table between the input IDs andrespective vowels in a Japanese character input mode.

In this correspondence table in FIG. 65, “a, i, u, e, o” and smallcharacters such as “small ya”, “small yu”, “small yo”, etc. are assignedto respective vowels as vowel IDs. Additionally, in the case of theJapanese character input mode, the vowel ID “a” is associated with theinput ID “2”, the vowel ID “i” with the input ID “3”, the vowel ID “u”with the input ID “6”, the vowel ID “o” with the input ID “8”, and thevowel ID “e” with the input ID “e”. Also, small characters areassociated with the input ID “4”.

FIG. 66 illustrates a correspondence table between consonant IDs andvowel IDs during a Japanese character input mode.

In other words, in this correspondence table in FIG. 66, the consonantIDs “a, k, s, t, n, h, m, y, r, w” correspond to respective “rows” ofthe gojuon syllabary, while the vowel IDs “a, i, u, e, o” corresponds torespective “columns” of the gojuon syllabary.

FIG. 67 illustrates a correspondence table between the input IDs andrespective numerals in a numeral input mode.

In other words, in this correspondence table in FIG. 67, the respectivenumerals and two symbols “0, 1, 2, 3, 4, 5, 6, 7, 8, 9, *, #” areassigned to the respective input IDs “0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11,12”.

FIG. 68 illustrates a correspondence table with the IDs of respectivemenu groups in the case where the menu selection discussed earlier isconducted.

In this correspondence table illustrated in FIG. 68, the group ID is anID individually assigned to respective menu groups during menu selection(group ID). In the case of the present embodiment, the group ID “2” isassociated with the input ID “2”, the group ID “4” with the input ID“4”, the group ID “6” with the input ID “6”, and the group ID “8” withthe input ID “8”, respectively. Meanwhile, it is configured such thatvarious applied uses such as the function information, etc. discussedearlier are applicable to the other input IDs.

FIG. 69 illustrates a correspondence table between the input IDs and IDscorresponding to menu items belonging to respective group IDs referencedfrom the correspondence table in FIG. 68 (internal group IDs) in thecase where menu selection is conducted.

Also, respective menu items like those illustrated by the correspondencetable in FIG. 70 are respectively associated with the internal group IDsfor menus illustrated in FIG. 69 as an example. Herein, in the case ofthis example, the respective menu items correspond to control itemsduring music playback as an example.

In other words, in the case of exemplary menu operations related tomusic playback, a “Play” menu item with the internal group ID “No. 2”, a“Pause” menu item with the internal group ID “No. 4”, an “Off” menu itemwith the internal group ID “No. 6”, and a “Stop” menu item with theinternal group ID “No. 8” are respectively associated with the groupwith the group ID “1”, as illustrated by the correspondence table inFIG. 70. Similarly, a “Play first” menu item with the internal group ID“No. 2”, a “Play from beginning” menu item with the internal group ID“No. 4”, a “Skip” menu item with the internal group ID “No. 6”, and a“Random” menu item with the internal group ID “No. 8” are associatedwith the group with the group ID “4”. A “Frame step back” menu item withthe internal group ID “No. 2”, a “Rewind” menu item with the internalgroup ID “No. 4”, a “Fast forward” menu item with the internal group ID“No. 6”, and a “Frame step forward” menu item with the internal group ID“No. 8” are associated with the group with the group ID “6”. An “Auto”menu item with the internal group ID “No. 2”, a “Low” menu item with theinternal group ID “No. 4”, a “High” menu item with the internal group ID“No. 6”, and a “Mute” menu item with the internal group ID “No. 8” areassociated with the group with the group ID “8”.

By referencing respective correspondence tables like those discussedabove, a mobile information device of the present embodiment computes aninput ID from a flick gesture direction, and also computes a respectivegroup ID and internal group ID for a respective operational mode fromthat input ID. Thus, a mobile information device of the presentembodiment becomes capable of realizing processing for English characterinput, Japanese character input, numeral input, menu selection,information search, etc. like that discussed earlier.

Herein, in the respective correspondence tables discussed above, it isalso possible to add new function assignments whereby what is called an“Undo” or other function is executed when a second action is selected bya tap, for example, by utilizing the empty parts in cases where thereare combinations for which ID, etc. assignments do not yet exist.

(Process Flow when Executing Information Input Control Program)

Hereinafter, a process flowchart will be described for when a mobileinformation device of the present embodiment executes an informationinput control program of the present embodiment and conducts processingfor the English character input, Japanese character input, numeralinput, menu selection, information search, etc. discussed earlier.Herein, an information input control program of the present embodimentmay be prepared at the time of factory shipment of a mobile informationdevice. Also, a mobile information device is made to be capable ofseparately obtaining an information input control program of the presentembodiment via the communication, external memory, external input andoutput terminals, etc., for example.

FIGS. 71 to 78 illustrate process flows for when a control-computationunit 104 in a mobile information device of the present embodimentexecutes an information input control program of the present embodiment.Herein, an information input control program in this case may beactivated according to instructions from the user, or automaticallyactivated at power on.

FIG. 71 and FIG. 72 are flowcharts that illustrate the flow of a seriesof processes during information input of characters, etc. in the presentembodiment.

Herein, while details will be described with the following flowcharts,with information input of characters, etc. in the present embodiment,input IDs are individually assigned to flick gestures, and additionally,depending on the conditions of the prior stack, divided into the groupIDs, consonant IDs, vowel IDs, etc. discussed earlier, for example.After that, input processing of characters, etc. is conducted by IDaddition processing discussed later.

For example, as discussed earlier, English character input is conductedby two flicks per English character, wherein a character is input byselecting the group in which exists the character that the user wants toinput (group ID) by a first flick, and selecting the character in thatgroup that the user wants to input (internal group ID) by a secondflick. Furthermore, the input ID, group ID, and internal group ID arestacked with each flick, and conversion from this stack to a characteris conducted. As another example, as discussed earlier, Japanesehiragana input is conducted by two flicks per hiragana character, wherethe consonant of the character that the user wants to input is selectedwith a first flick, and the ID of that consonant is stacked. A vowel isselected with a second flick, and the ID of that vowel is stacked. Then,conversion from the stacked consonant ID and vowel ID into a characteris conducted. For example, as discussed earlier, numeral input isconducted by one flick per numeral character. As another example, asdiscussed earlier, menu item selection is conducted by refining in orderfrom the top menu tier by flicks. As a further example, as discussedearlier, information search from a phone book, etc. is conducted byrefining relevant phone book records by a plurality of flicks, andcausing selection when the number of search result records becomessmaller (or when the search results are refined to one).

In the flowchart in FIG. 71, an information input control program of thepresent embodiment is taken to be already activated, and thecontrol-computation unit 104 has entered a standby state for a useroperation on a touch panel in the case where for example the mobileinformation device enters a viewing mode for a browser screen includinga text box like that discussed earlier as step S1.

Herein, in the case where for example as step S2 a touch panel istouched by the user, and the touch position was the text box, as theprocessing in step S3 the control-computation unit 104 transitions tothe full screen takeover mode. Also, as step S4, at this time thecontrol-computation unit 104 transitions to a character input modewhereby character input is made into the text box.

Upon transitioning to the character input mode, the control-computationunit 104 enters a standby state for a user operation on the touch panelin the full screen takeover mode. Then, if some kind of action from theuser is performed as step S5, as the processing in step S6 thecontrol-computation unit 104 determines whether that action is an inputevent with respect to a touch panel, or an input event on a physicalkey.

In the case where it is determined that the user action was an inputevent such as for example a press operation on a physical key, as theprocessing in step S7 the control-computation unit 104 cancels the fullscreen takeover mode while also returning from a character input mode toa browser viewing mode, and returns the process to step S1.

In contrast, in the case where it is determined that the user action wasan input event on a touch panel, the control-computation unit 104advances the process to step S8.

Advancing to the processing in step S8, in the case where a touch eventwherein the user's finger, etc. contacts the touch panel is detected asthe determined input event, as the processing in step S9 thecontrol-computation unit 104 determines which area on the touch panel isthe area touched by the touch event.

Then, the control-computation unit 104 advances the process to step S15in FIG. 72 discussed later in the case where it is determined that thetouched area is for example the convert/symbol instruction area 14 fromamong the function areas 12 to 15.

In contrast, the control-computation unit 104 advances the process tostep S10 in the case where it is determined that the touched area is anarea enabling information input of characters, etc. by the flickgestures, etc., or in other words is for example an area on the touchpanel excluding the function areas 12 to 15.

Advancing to the processing in step S10, the control-computation unit104 determines whether or not the touch event on the touch panel is thetap gesture.

The control-computation unit 104 advances the process to step S12 in thecase where it is determined in the determination processing of the abovestep S10 that the touch event is not a tap gesture, or in other words isa flick gesture, for example.

Advancing to the processing in step S12, the control-computation unit104 computes a velocity vector for the flick gesture, and also detects aflick direction from that velocity vector.

Next, as the processing in step S13, the control-computation unit 104references the ID discussed earlier that matches the direction of theflick from a correspondence table discussed earlier, and advances theprocess to step S14. Herein, in the case where the flick gesture is afirst flick gesture, the ID becomes an input ID and a group IDcorresponding to that input ID.

Also, the control-computation unit 104 advances the process to step S11in the case where it is determined in step S10 that the touch event is atap gesture.

Advancing to the processing in step S11, the ID corresponding to thattap gesture is referenced from a correspondence table discussed earlier,and the process is advanced to step S14. Herein, the ID corresponding toa tap gesture in this case becomes the input ID and the group IDcorresponding to that input ID.

Advancing to the processing in step S14, the control-computation unit104 retains the ID as stack data, and then returns the process to stepS5. Herein, the processing in step S14 differs according to whether theoperational mode is the English character input mode, the Japanesecharacter input mode, the numeral input mode, the menu selection mode,or the phone book search mode discussed earlier. The details thereofwill be discussed later.

After the process is returned to step S5, in the case where it isdetermined in step S10 that the touch event is a second flick gesture,the ID referenced in step S13 becomes an internal group ID.

Next, the process advances to step S15 in FIG. 72 and thecontrol-computation unit 104 transitions to a conversion mode due to itbeing determined in step S9 that the touched area is the convert/symbolinstruction area 14. Herein, the conversion mode is a mode used duringthe kana-kanji conversion of a Japanese character input mode, forexample. In this example of the flowchart in FIG. 72, kana-kanjiconversion in a Japanese character input mode is given by way ofexample.

Upon transitioning to a conversion mode in step S15 in FIG. 72, thecontrol-computation unit 104 advances to the processing in step S16.Upon advancing to the processing in step S16, the control-computationunit 104 extracts conversion candidates like those discussed earlier onthe basis of an unconfirmed character string input by the previous groupselection, etc., as conversion candidate extraction processing.

Next, as the processing in step S17, the control-computation unit 104displays a list of the conversion candidates extracted in the previousstep S16 on a display screen, and then advances the process to step S18.

Upon advancing to the processing in step S18, the control-computationunit 104 enters a standby state for a user operation on the touch panel.When some kind of action from the user is detected in S19 and thataction is a flick gesture with respect to a touch panel, as theprocessing in step S20 the control-computation unit 104 determines thedirection of that flick gesture.

Then, in the case where the direction of the flick is the upward ordownward direction, as the processing in step S21 thecontrol-computation unit 104 scrolls the candidate list in the upward ordownward direction on a screen, and then returns the process to stepS17.

Also, in the case where the direction of the flick is leftward, thecontrol-computation unit 104 returns the process to step S4 in FIG. 71.

Also, in the case where the orientation row of the flick is rightward,as the processing in step S22 the control-computation unit 104substitutes the conversion candidate selected by the rightward flickgesture into a text box.

After that, as the processing in step S23 the control-computation unit104 determines whether or not the character string that has been inputup to this time is in a stacked character string state having anunconfirmed character string that should be additionally converted. Thecontrol-computation unit 104 returns the process to step S16 in the caseof an unconfirmed character string, and in contrast, returns the processto step S4 in FIG. 71 in the case of no unconfirmed character string tobe converted.

FIG. 73 illustrates a detailed process flow for the step S14 part of theabove FIG. 71 in the case where a character input mode is an Englishcharacter input mode.

In an English character input mode, upon advancing to the processing instep S14 in FIG. 73, as the processing in step S30 thecontrol-computation unit 104 determines whether the stack data at theend of the stacked data discussed earlier is an English characterdiscussed earlier or an ID (group ID). The control-computation unit 104advances the process to step S32 in the case of a group ID.

Advancing to the processing in step S32, the control-computation unit104 conducts conversion from an input ID to an internal group ID byreferencing the correspondence table for English character inputdiscussed earlier.

Next, as the processing in step S33, the control-computation unit 104references the correspondence table for English character input anddetermines an English character from the previously selected group IDand the internal group ID. Then, as the processing in step S34, thecontrol-computation unit 104 stacks that English character data as stackdata.

In contrast, if it is determined in step S30 that the stack data at theend is an English character, the control-computation unit 104 advancesthe process to step S31.

Advancing to the processing in step S31, the control-computation unit104 references the correspondence table for English character input anddetermines a group ID from an input ID. Then, as the processing in stepS34, the control-computation unit 104 stacks a group ID as stack data.

After that, the control-computation unit 104 returns the process to stepS5 in FIG. 71.

FIG. 74 illustrates a detail process flow for the step S14 part of FIG.71 in the case where a character input mode is a Japanese characterinput mode.

In a Japanese character input mode, upon advancing to the processing instep S14 in FIG. 74, as the processing in step S40, thecontrol-computation unit 104 determines whether the stack data at theend of the stacked data discussed earlier is a hiragana characterdiscussed earlier or a consonant ID. The control-computation unit 104advances the process to step S42 in the case of a consonant ID.

Upon advancing to the processing in step S42, the control-computationunit 104 conducts conversion from an input ID to a vowel ID byreferencing the correspondence table for Japanese character inputdiscussed earlier.

Next, as the processing in step S43, the control-computation unit 104references the correspondence table for Japanese character inputdiscussed earlier and determines a hiragana character from thepreviously selected consonant ID and vowel ID. Then, as the processingin step S34, the control-computation unit 104 stacks that hiraganacharacter data as stack data.

In contrast, in the case where it is determined in step S40 that thestack data at the end is a hiragana character, the control-computationunit 104 advances the process to step S41.

Advancing to the processing in step S41, the control-computation unit104 references the correspondence table for Japanese character input anddetermines a consonant ID from an input ID. Then, as the processing instep S44, the control-computation unit 104 stacks a consonant ID asstack data.

After that, the control-computation unit 104 returns the process to stepS5 in FIG. 71.

FIG. 75 illustrates a detailed process flow for the step S14 part ofFIG. 71 in the case where a character input mode is a numeral inputmode.

In a numeral input mode, upon advancing to the processing in step S14 inFIG. 75, as the processing in step S50, the control-computation unit 104references the correspondence table for a numeral input mode discussedearlier, and conducts conversion from an input ID to a numeral.

Then, as the processing in step S51, the control-computation unit 104substitutes the numeral determined in step S50 into a text box.

Next, as the processing in step S43, the control-computation unit 104references the correspondence table for Japanese character input anddetermines a hiragana character from the previously selected consonantID and vowel ID. Then, as the processing in step S34, thecontrol-computation unit 104 stacks that hiragana character as stackdata.

In contrast, in the case where it is determined in step S40 that thestack data at the end is a hiragana character, the control-computationunit 104 advances the process to step S41.

Advancing to the processing in step S41, the control-computation unit104 references the correspondence table for Japanese character input anddetermines a consonant ID from an input ID. Then, as the processing instep S44, the control-computation unit 104 stacks a consonant ID asstack data.

After that, the control-computation unit 104 returns the process to stepS5 in FIG. 71.

FIG. 76 illustrates a detailed process flow for the step S14 part ofFIG. 71 in the case where the operational mode is a menu item selectioninput mode.

In a menu selection mode, upon advancing to the processing in step S14in FIG. 76, as the processing in step S60, the control-computation unit104 determines whether the stack data at the end of the stacked datadiscussed earlier is in a blank state or a group ID. Thecontrol-computation unit 104 advances the process to step S63 in thecase of a group ID.

Upon advancing to the processing in step S63, the control-computationunit 104 conducts conversion from an input ID to an internal group ID byreferencing the correspondence table for menu selection discussedearlier.

Next, as the processing in step S64, the control-computation unit 104references the correspondence table for menu selection, and executesprocessing according to a menu item obtained from the previouslyselected group ID and internal group ID. Then, as the processing in stepS65, the control-computation unit 104 clears the stack data and thenreturns the process to step S5 in FIG. 71.

In contrast, in the case where it is determined in step S60 that thestack data at the end is blank, the control-computation unit 104advances the process to step S61.

Upon advancing to the processing in step S61, the control-computationunit 104 references the correspondence table for menu selection anddetermines a group ID from an input ID. Then, as the processing in stepS62, the control-computation unit 104 stacks a group ID as stack data.

After that, the control-computation unit 104 returns the process to stepS5 in FIG. 71.

FIG. 77 illustrates a detailed process flow for the step S14 part ofFIG. 71 in the case where the operational mode is the phone bookinformation search mode discussed earlier.

In a phone book information search mode, upon advancing to theprocessing in step S14 in FIG. 77, as the processing in step S70, thecontrol-computation unit 104 executes phone book registered recordsearch processing, and advances the process to step S71.

Upon advancing to the processing in step S71, the control-computationunit 104 determines whether or not the number of search result recordsis greater than 4, for example. The control-computation unit 104advances the process to step S72 in the case of greater than 4, and incontrast, advances the process to step S74 in the case of 4 or less.

Upon advancing to the processing in step S72, the control-computationunit 104 executes input ID to English character conversion processing,and stacks that data as stack data.

In contrast, upon advancing to the processing in step S74, thecontrol-computation unit 104 converts an input ID into a candidatenumber. Next, as the processing in step S75, a record is specified fromthe records found by search and a candidate number.

Then, the control-computation unit 104 displays the specified phone bookinformation on a display screen.

After that, the control-computation unit 104 returns the process to stepS5 in FIG. 71.

FIG. 78 illustrates a flowchart of a process flow when inputting desiredinformation by the consecutive flick gestures discussed earlier.

After processing similar to step S1 to step S3 in FIG. 71 is performed,when the process advances to step S80 in FIG. 78, thecontrol-computation unit 104 transitions to a character input modewhereby character input is made into the text box.

After transitioning to the character input mode, the control-computationunit 104 enters a standby state for a user operation on the touch panelin the full screen takeover mode. The, if some kind of user action isperformed as step S81, as the processing in step S82 thecontrol-computation unit 104 determines whether that action is an inputevent with respect to a touch panel, or an input event on a physicalkey.

In the case where it is determined that the user action was an inputevent such as for example a press operation on a physical key, as theprocessing in step S83 the control-computation unit 104 cancels the fullscreen takeover mode while also returning from a character input mode toa browser viewing mode, and returns to processing similar to step S1discussed earlier.

In contrast, in the case where it is determined that the user action wasan input event on a touch panel, the control-computation unit 104advances the process to step S84.

Advancing to the processing in step S84, in the case where a touch eventwherein the user's finger, etc. contacts the touch panel is detected asthe determined input event, as the processing in step S85 thecontrol-computation unit 104 determines which area on the touch panel isthe area touched by the touch event.

Then, the control-computation unit 104 advances the process to a stepS15 similar to FIG. 72 discussed later in the case where it isdetermined that the touched area is for example the convert/symbolinstruction area 14 from among the function areas 12 to 15.

In contrast, the control-computation unit 104 advances the process tostep S86 in the case where it is determined that the touched area is anarea enabling information input of characters, etc. by the flickgestures, etc.

Advancing to the processing in step S86, the control-computation unit104 determines whether or not the touch event on the touch panel is thetap gesture.

The control-computation unit 104 advances the process to step S88 in thecase where it is determined in the determination processing of the abovestep S86 that the touch event is not a tap gesture, or in other words isa flick gesture, for example.

Advancing to the processing in step S88, the control-computation unit104 computes a velocity vector for the flick gesture, and also detects aflick direction from that velocity vector.

Next, as the processing in step S89, the control-computation unit 104references the ID discussed earlier that matches the direction of theflick from a correspondence table discussed earlier, and advances theprocess to step S90. Herein, in the case where the flick gesture is afirst flick gesture, the ID becomes an input ID and a group IDcorresponding to that input ID.

Also, the control-computation unit 104 advances the process to step S87in the case where it is determined in step S86 that the touch event is atap gesture.

Advancing to the processing in step S87, the ID corresponding to thattap gesture is referenced from a correspondence table discussed earlier,and the process is advanced to step S90. Herein, the ID corresponding toa tap gesture in this case becomes the input ID and the group IDcorresponding to that input ID.

Advancing to the processing in step S90, the control-computation unit104 retains the ID as stack data, and then advances the process to stepS91. Herein, the processing in step S90 is similar to step S14 discussedearlier.

Advancing to the processing in step S91, the control-computation unit104 determines whether or not the user's finger was released from atouch panel. The control-computation unit 104 returns the process tostep S81 in the case where it is determined that the finger wasreleased, and advances the process to step S92 in the case where it isdetermined that the finger was not released.

Advancing to the processing in step S92, if the control-computation unit104 detects a change in the velocity direction given by a flick gestureperformed in a state where a finger is not released from the touchpanel, the control-computation unit 104 advances the process to stepS93.

Advancing to the processing in step S93, the control-computation unit104 computes a velocity vector after the velocity direction changed, andalso detects a flick direction from that velocity vector.

Then, as the processing in step S94, the control-computation unit 104references an ID discussed earlier that matches the direction of theflick from a correspondence table discussed earlier, and then advancesthe process to step S90.

CONCLUSION

A mobile information device in accordance with an embodiment of thepresent disclosure as described above includes an input operation unitthat includes a detection surface able to detect operation input by auser, an information assignment control unit that assigns respectivegiven information to a plurality of directions on the detection surfaceapproximately centered on a user-desired operation input position on thedetection surface, and an information input control unit that inputsgiven information assigned to an approximately matching direction asinformation selected by the user when an operation input direction givenby the user on the detection screen of the input operation unitapproximately matches one of the plurality of directions assigned withthe given information by the information assignment control unit.

Herein, in a mobile information device of the present embodiment, thedetection surface of the input operation unit may for example consist ofa transparent panel able to detect operation input by the user, and beprovided approximately parallel to a display surface of a display unitprovided with a display surface approximately the same as the detectionsurface.

Also, in a mobile information device of the present embodiment, theinformation assignment control unit may for example also assign giveninformation to a user-desired operation input position on the detectionsurface. Then, in this case, the information input control unit inputsinformation assigned to the operation input position as informationselected by the user when operation input given by the user on thedetection surface of the input operation unit is a prescribed operationwith respect to the user-desired operation input position.

Also, in a mobile information device of the present embodiment, thegiven information may for example be information tiered in a pluralityof character groups consisting of a plurality of character information,and respective character information belonging to each of thosecharacter groups. Then, in this case, the information assignment controlunit assigns respective character groups to the respective directionsaccording to operation input at a user-desired position on the detectionscreen, and when an operation input direction given by the userapproximately matches one of the plurality of directions assigned withthe character groups by the information assignment control unit, theinformation input control unit takes the character group assigned to theapproximately matching direction as a character group selected by theuser. Subsequently, after selection of the character group has beenmade, the information assignment control unit assigns respectivecharacter information belonging to the selected character group to therespective directions according to operation input at a user-desiredposition on the detection screen, and when an operation input directiongiven by the user approximately matches one of the plurality ofdirections assigned with the character information by the informationassignment control unit, the information input control unit takes thecharacter information assigned to the approximately matching directionas character information selected by the user.

Also, in a mobile information device of the present embodiment, thegiven information may for example be information tiered in a pluralityof consonant information and a plurality of vowel information. Then, inthis case, the information assignment control unit assigns respectiveconsonant information to the respective directions according tooperation input at a user-desired position on the detection screen, andwhen an operation input direction given by the user approximatelymatches one of the plurality of directions assigned with the consonantinformation by the information assignment control unit, the informationinput control unit takes the consonant information assigned to theapproximately matching direction as consonant information selected bythe user. Subsequently, after selection of the consonant information hasbeen made, the information assignment control unit assigns the selectedconsonant information to the respective directions according tooperation input at a user-desired position on the detection screen, andwhen an operation input direction given by the user approximatelymatches one of the plurality of directions assigned with the vowelinformation by the information assignment control unit, the informationinput control unit takes the vowel information assigned to theapproximately matching direction as vowel information selected by theuser, and takes character information consisting of a combination of theconsonant information and vowel information as input information.

Also, in a mobile information device of the present embodiment, thegiven information may for example consist of a plurality of numeralinformation. Then, in this case, according to operation input at auser-desired position on the detection screen, the informationassignment control unit assigns respective numeral information to theuser-desired operation input position and the respective directions.Furthermore, when an operation input given by the user on the detectionscreen of the input operation unit is a prescribed operation withrespect to the user-desired operation input position, the informationinput control unit takes information assigned to the operation inputposition as numeral information selected by the user, and when anoperation input given by the user on the detection screen of the inputoperation unit is an operation input direction that approximatelymatches one of the plurality of directions, the information inputcontrol unit takes the numeral information assigned to the approximatelymatching direction as numeral information selected by the user.

Also, in a mobile information device of the present embodiment, thegiven information may for example be information tiered in a pluralityof menu groups consisting of a plurality of menu informationcorresponding to respective given functions, and respective menuinformation belonging to each of those menu groups. Then, in this case,the information assignment control unit assigns respective menu groupsto the respective directions according to operation input at auser-desired position on the detection screen, and when an operationinput direction given by the user approximately matches one of theplurality of directions assigned with the menu groups by the informationassignment control unit, the information input control unit takes themenu group assigned to the approximately matching direction as a menugroup selected by the user. Subsequently, after selection of the menugroup has been made, the information assignment control unit assignsrespective menu information belonging to the selected menu group to therespective directions according to operation input at a user-desiredposition on the detection screen, and when an operation input directiongiven by the user approximately matches one of the plurality ofdirections assigned with the menu information by the informationassignment control unit, the information input control unit takes themenu information assigned to the approximately matching direction asmenu information selected by the user.

Also, in a mobile information device of the present embodiment, thegiven information may for example be storage-related information relatedto stored information inside a given information storage unit. Then, inthis case, the information assignment control unit assigns respectivestorage-related information to the respective directions according tooperation input at a user-desired position on the detection screen.Furthermore, when an operation input direction given by the userapproximately matches one of the plurality of directions assigned withthe storage-related information by the information assignment controlunit, the information input control unit takes the storage-relatedinformation assigned to the approximately matching direction asstorage-related information selected by the user, and extracts thestored information from the given information storage unit on the basisof that storage-related information.

Also, the given information storage unit may for example be a phone bookinformation storage unit that takes registered information in a phonebook as the stored information. Then, in this case, the storage-relatedinformation is information for specifying the registered information ina phone book.

Also, in an information input method of an embodiment of the presentdisclosure, when operation input is made with respect to a user-desiredposition on a detection surface with respect to an input operation unitthat includes a detection surface able to detect operation input by auser, an information assignment control unit assigns respective giveninformation to a plurality of directions on the detection surfaceapproximately centered on the user-desired operation input position, andwhen an operation input direction given by the user on the detectionscreen of the input operation unit approximately matches one of theplurality of directions assigned with given information by theinformation assignment control unit, an information input control unitinputs given information assigned to the approximately matchingdirection as information selected by the user.

Also, an information input control program of an embodiment of thepresent disclosure causes a computer installed in a mobile informationdevice to function as an information assignment control unit thatassigns respective given information to a plurality of directions on adetection surface approximately centered on a user-desired operationinput position when operation input is made with respect to auser-desired position on a detection surface with respect to an inputoperation unit that includes a detection surface able to detectoperation input by a user, and an information input control unit thatinputs given information assigned to an approximately matching directionas information selected by the user when an operation input directiongiven by the user on the detection screen of the input operation unitapproximately matches one of the plurality of directions assigned withthe given information by the information assignment control unit.

Also, a storage medium of an embodiment of the present disclosure isrealized by storing an information input control program that causes acomputer installed in a mobile information device to function as aninformation assignment control unit that assigns respective giveninformation to a plurality of directions on a detection surfaceapproximately centered on a user-desired operation input position whenoperation input is made with respect to a user-desired position on adetection surface with respect to an input operation unit that includesa detection surface able to detect operation input by a user, and aninformation input control unit that inputs given information assigned toan approximately matching direction as information selected by the userwhen an operation input direction given by the user on the detectionscreen of the input operation unit approximately matches one of theplurality of directions assigned with the given information by theinformation assignment control unit.

Additionally, in the present embodiment, input of characters, menuselection, information search, etc. is possible just with at least onetap gesture and flick gesture. Also, in the present embodiment,association between for example flick gesture directions and what iscalled a keypad layout is made to be possible, enabling desiredinformation input by flick directions from the center key (for example,the “5” key on a keypad).

In other words, according to the present embodiment, the user becomesable to input the desired place of characters, etc. by touching anarbitrary place on a touch panel (display screen) that has entered afull screen takeover mode, without doing work such as touching a virtualkey displayed on a display screen after visually confirming that virtualkey. Consequently, the user is able to input at an arbitrary placewithout needing to confirm the place to be touched, even if the user issomeone for whom input in small places is difficult, such as a user whooften inputs with the pad of his or her finger because his or herfingernails are long, for example.

Also, according to the present embodiment, in the case where flickdirections and a keypad layout are approximately associated, the user isable to conduct input without looking at the screen by memorizing thekeypad layout.

Also, according to the present embodiment, there is extremely littleguide information displayed on screen during input. For this reason, thedisplay screen is not occupied by guide information, and the user isable to perform input comfortably.

Also, according to the present embodiment, the device that detects theuser's gesture operations is not limited to being a touch panel (touchscreen), and may be any device such as what is called a touch pad, forexample, as long as it is a device capable of detecting flick gestures.

Also, in the case of the present embodiment, since operations other thaninput of characters, etc. are made to be prevented by a full screentakeover mode, it is possible to prevent accidental operations wherebyanother function such as jumping to a link destination, for example, isaccidentally executed.

Furthermore, in the present embodiment, in the case where informationinput is performed by the consecutive flick gestures discussed earlier,the user becomes able to input desired information without releasing hisor her finger from a touch panel.

As discussed above, according to the present embodiment, in aninformation device provided with a touch panel, etc. on a display panel,for example, the work of visual confirmation by the user can bedecreased and also the burden of timing matching during input is mostlymade unnecessary in the case of inputting characters, etc. using thetouch panel. An information input apparatus enabling a significantreduction in user burden is provided.

Meanwhile, a mobile information device of the present embodiment is alsoapplicable to a smartphone, or for example a PDA (Personal DigitalAssistant) or compact notebook type personal computer, a portable gameconsole, a tablet device portable navigation device, etc.

Also, the description of the embodiment discussed above is one exampleof the present disclosure. For this reason, the present disclosure isnot limited to embodiment discussed above, and it is obvious thatvarious modifications depending on the design, etc. are possible ifwithin a scope that does not depart from the technical ideas inaccordance with the present disclosure.

Furthermore, it is to be understood by those skilled in the art thatvarious modifications, combinations, and other embodiments may occurdepending on the design and other factors insofar as they are within thescope of the claims of the present disclosure or equivalents thereof.

What is claimed is:
 1. An information input apparatus comprising: a userinterface configured to detect a first input operation; a processorconfigured to assign information to each of a plurality of directionsfrom a position centered at the first input operation detected by theuser interface, wherein the user interface is configured to detect asecond input operation corresponding to one of the plurality ofdirections, and the processor is configured to select informationassigned to the one of the plurality of directions as an input.
 2. Theinformation input apparatus of claim 1, wherein the user interfaceincludes a transparent panel configured to detect a touch input.
 3. Theinformation input apparatus of claim 1, wherein the user interfaceincludes a display surface configured to be controlled by the processor.4. The information input apparatus of claim 1, wherein the processor isconfigured to control the user interface to display the informationassigned to each of the plurality of directions when the user interfacedetects the first input operation.
 5. The information input apparatus ofclaim 1, wherein the information assigned to each of the plurality ofdirections includes a character group identifying a plurality ofcharacters.
 6. The information input apparatus of claim 5, wherein theprocessor is configured to select a character group assigned to the oneof the plurality of directions corresponding to the second inputoperation.
 7. The information input apparatus of claim 6, wherein theprocessor is configured to assign each of the characters included in theselected character group to one of the plurality of directions.
 8. Theinformation input apparatus of claim 7, wherein the processor isconfigured to control the user interface to display each of thecharacters identified by the selected character group assigned to eachof the plurality of directions.
 9. The information input apparatus ofclaim 7, wherein the user interface is configured to detect a thirdinput operation by the user corresponding to one of the plurality ofdirections.
 10. The information input apparatus of claim 9, wherein theprocessor is configured to select the character assigned to the one ofthe plurality of directions corresponding to the third input operationas an input.
 11. The information input apparatus of claim 1, wherein theinformation assigned to each of the plurality of directions includesmenu items configured to control reproduction of at least one of audioand video content.
 12. The information input apparatus of claim 11,wherein the processor is configured to control the user interface todisplay the menu items assigned to each of the plurality of directionswhen the user interface detects the first input operation.
 13. Theinformation input apparatus of claim 11, wherein the informationassigned to at least one of the plurality of directions includes a menugroup identifying a plurality of menu items.
 14. The information inputapparatus of claim 13, wherein the processor is configured to select themenu function or the menu group corresponding to the second inputoperation as an input.
 15. The information input apparatus of claim 14,wherein, when the selected direction corresponds to the menu group, theprocessor is configured to assign each of the plurality of menu itemsidentified by the menu group to one of the plurality of directions. 16.The information input apparatus of claim 15, wherein the processor isconfigured to control the user interface to display each of the menuitems identified by the selected menu group assigned to each of theplurality of directions.
 17. The information input apparatus of claim15, wherein the user interface is configured to detect a third inputoperation by the user corresponding to one of the plurality ofdirections.
 18. The information input apparatus of claim 17, wherein theprocessor is configured to select the menu item assigned to the one ofthe plurality of directions corresponding to the third input operationas an input.
 19. A method of controlling a user interface of aninformation input apparatus, the method comprising: detecting, at a userinterface of the information input apparatus, a first input operation bya user; assigning, by a processor of the information input apparatus,information to each of a plurality of directions from a position of thefirst input operation detected by the user interface; detecting, by theuser interface, a second input operation by the user corresponding toone of the plurality of directions; and selecting, by the processor,information assigned to the one of the plurality of directions as aninput.
 20. A non-transitory computer-readable medium including computerprogram instructions, which when executed by an information inputapparatus, cause the information input apparatus to perform a method,the method comprising: detecting a first input operation by a user;assigning information to each of a plurality of directions from aposition of the first input operation detected by the user interface;detecting a second input operation by the user corresponding to one ofthe plurality of directions; and selecting information assigned to theone of the plurality of directions as an input.